connectors_update_connection
Rename, activate/deactivate, or reconfigure a connection. When passing
This record as markdown: /tools/com-getmunin-munin/connectors-update-connection.md
What connectors_update_connection does on Munin
AI agents use connectors_update_connection to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.
Why connectors_update_connection is rated Medium
Modifies connector configurations; impacts integrations but reversible and bounded by existing connections.
From the tool's definition Rename, activate/deactivate, reconfigure a connection
Attacks that exploit this kind of access
The rule that runs connectors_update_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For connectors_update_connection, this is the rule to start with:
connectors_update_connection stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every connectors_update_connection call is checked against it from then on.
Questions about connectors_update_connection
Rename, activate/deactivate, or reconfigure a connection. When passing. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Munin MCP server in PolicyLayer and add a rule for connectors_update_connection: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Munin. Nothing to install.
connectors_update_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connectors_update_connection rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for connectors_update_connection. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
connectors_update_connection is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue