Deletes a specific connector from the current board.
AI agents call delete_connector to permanently remove resources in Miro MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a connector object from the board. While the blast radius is contained to a single connector (not a complete board wipe), deletion operations cannot be undone without manual restoration or undo functionality, making it destructive rather than write.
From the tool's definition Tool name is 'delete_connector' and description states it 'Deletes a specific connector from the current board.' The verb 'deletes' and the irreversible nature of removing a connector from a Miro board clearly indicate destructive capability.
Documented attack patterns abuse exactly the kind of access delete_connector gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Miro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_connector:
{
"version": "1",
"default": "deny",
"hide": [
"delete_connector"
]
} delete_connector disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a specific connector from the current board. It is categorised as a Destructive tool in the Miro MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Miro MCP Server MCP server in PolicyLayer and add a rule for delete_connector: 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 Miro MCP Server. Nothing to install.
delete_connector is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_connector 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 delete_connector. 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.
delete_connector is provided by the Miro MCP Server MCP server (luotocompany/mcp-server-miro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Miro MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 Miro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.