Create a connector/line between two existing items (CRITICAL: both items must already exist on the board)
AI agents use create_connector to create or update resources in Miro MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Miro MCP Server environment.
This tool creates new connectors/lines on a Miro board, which is a reversible write operation. It modifies board state by adding visual connections between existing items, but does not delete, execute code, move money, or cause irreversible changes. The constraint that both items must exist limits unintended consequences.
From the tool's definition Tool name 'create_connector' and description 'Create a connector/line between two existing items' indicates creation/modification of board content. Requires both items to already exist, preventing cascading effects.
Attacks that exploit this kind of access
Create a connector/line between two existing items (CRITICAL: both items must already exist on the board). It is categorised as a Write tool in the Miro MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Miro MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_connector 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 create_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 create_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.
create_connector is provided by the Miro MCP Server MCP server (soul-script/miro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →