What happened?
we have added a custom connector
steps
- go to the connectors list
- choose the connector and click on connect, authenticator and get the list of tools
- for all read only tools, we have allow always
- go to the chat
- ask a question for the MCP. claude still asks permission (allow once, allow always). though allow all is given in the connector level, still in the chat it asks for the permission
- when we turn off the connector in the chat (i., toggle on or off the connector in the chat, not session disconne). it resets back to needs approval. but sometimes whatever permission in the chat it overrides
- this is very inconsistant. sometimes it works as expected somtimes not
What did you expect to happen?
- set permission in the connector level
- chat should adhire to that
- turn on or off the connector, still connector retain the permission what is being set by the user. it should not back to default state.
Steps to reproduce
we have added a custom connector
steps
- go to the connectors list
- choose the connector and click on connect, authenticator and get the list of tools
- for all read only tools, we have allow always
- go to the chat
- ask a question for the MCP. claude still asks permission (allow once, allow always). though allow all is given in the connector level, still in the chat it asks for the permission
- when we turn off the connector in the chat (i., toggle on or off the connector in the chat, not session disconne). it resets back to needs approval. but sometimes whatever permission in the chat it overrides
- this is very inconsistant. sometimes it works as expected somtimes not
Area
MCP Connector (adding/managing servers)
MCP Server (if applicable)
Amazon Bedrockagentcore
Error messages or logs
Additional context
No response
What happened?
we have added a custom connector
steps
What did you expect to happen?
Steps to reproduce
we have added a custom connector
steps
Area
MCP Connector (adding/managing servers)
MCP Server (if applicable)
Amazon Bedrockagentcore
Error messages or logs
Additional context
No response