// SCAN REPORT

Miro Server

97 tools. 55 can modify or destroy data without limits.

17 destructive tools with no built-in limits. Policy required.

Last updated: 20 May 2026

55 can modify or destroy data

42 read-only

97 tools total

Free to start. No card required.

TOOL MAP

Read (42) Write / Execute (38) Destructive / Financial (17)

WHAT CAN GO WRONG

Destructive tools (delete-app-card-item, delete-board, delete-card-item) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (add-project-member, attach-tag, copy-board) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

RECOMMENDED RULES

Deny destructive operations

{
  "delete-app-card-item": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add-project-member": {
    "limits": [
      {
        "counter": "add-project-member_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "detach-tag": {
    "limits": [
      {
        "counter": "detach-tag_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

ALL 97 MIRO SERVER TOOLS

DESTRUCTIVE 17 tools

WRITE 38 tools

Write add-project-member Write attach-tag Write copy-board Write create-app-card-item Write create-board Write create-board-export-job Write create-card-item Write create-connector Write create-document-item Write create-embed-item Write create-frame Write create-group Write create-image-item-using-file Write create-image-item-using-url Write create-items-in-bulk Write create-items-in-bulk-using-file Write create-mindmap-node Write create-shape-item Write create-sticky-note-item Write create-tag Write create-text-item Write update-app-card-item Write update-board Write update-board-classification Write update-board-member Write update-card-item Write update-connector Write update-document-item Write update-embed-item Write update-frame-item Write update-group Write update-image-item Write update-image-item-using-file Write update-item-position Write update-shape-item Write update-sticky-note-item Write update-tag Write update-text-item

READ 42 tools

Read detach-tag Read get-all-board-members Read get-all-cases Read get-all-groups Read get-all-legal-holds Read get-all-tags Read get-app-card-item Read get-audit-logs Read get-board-classification Read get-board-content-logs Read get-board-export-job-results Read get-board-export-job-status Read get-card-item Read get-case Read get-connectors Read get-document-item Read get-embed-item Read get-frame-item Read get-group Read get-group-items Read get-image-item Read get-item-tags Read get-items-on-board Read get-legal-hold Read get-legal-hold-content-items Read get-mindmap-node Read get-mindmap-nodes Read get-organization-info Read get-organization-member Read get-organization-members Read get-project-member Read get-shape-item Read get-specific-board Read get-specific-board-member Read get-specific-connector Read get-specific-item Read get-sticky-note-item Read get-tag Read get-text-item Read list-boards Read ungroup-items

FAQ

Can an AI agent delete data through the Miro Server MCP server? +

Yes. The Miro Server server exposes 17 destructive tools including delete-app-card-item, delete-board, delete-card-item. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Miro Server? +

The Miro Server server has 38 write tools including add-project-member, attach-tag, copy-board. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Miro Server.

How many tools does the Miro Server MCP server expose? +

97 tools across 3 categories: Destructive, Read, Write. 42 are read-only. 55 can modify, create, or delete data.

How do I enforce a policy on Miro Server? +

Register the Miro Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every Miro Server tool call.

Deterministic rules across all 97 Miro Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

SECURE MIRO SERVER →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

Miro Server

// TOOL MAP

// WHAT CAN GO WRONG

// RECOMMENDED RULES

// ALL 97 MIRO SERVER TOOLS

// FAQ