get_connector

THE RISK

Low Risk

Why get_connector needs a policy

This tool queries connector metadata without creating, modifying, deleting, or executing any operations. It is a simple read operation that returns information about an existing connector on a Miro board.

From the tool's definition Tool name 'get_connector' and description 'Retrieves information for a specific connector' indicate a data retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_connector gives an agent:

POLICY

How to control get_connector

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 get_connector:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_connector": {}
  }
}

get_connector is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Miro MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Miro MCP Server tools

Destructive delete_connector Deletes a specific connector from the current board. Destructive delete_item Deletes a specific item (sticky note, text, shape, card, document, embed, image, app card) Write create_app_card_item Adds an app card item to the board. Write create_card_item Adds a card item to the current board. Write create_connector Adds a connector between two items on the current board. Write create_document_item_using_url Adds a document item to the board using a URL. Write create_embed_item Adds an embed item (e.g., video, website) to the board. Write create_image_item_using_url Adds an image item to the board using a URL.

All 30 Miro MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_connector

What does the get_connector tool do? +

Retrieves information for a specific connector on the current board. It is categorised as a Read tool in the Miro MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_connector? +

Register the Miro MCP Server MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_connector? +

get_connector is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_connector? +

Yes. Add a rate_limit block to the get_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.

How do I block get_connector completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_connector? +

get_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.

Enforce policy on every Miro MCP Server tool call.

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.

CHECK YOUR STACK →