Critical-risk tools in Miro Server
17 of the 97 tools in Miro Server are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete-app-card-itemDestructive 4/5Delete a specific app card item from a Miro board
-
delete-boardDestructive 4/5Delete a Miro board by its ID. Deleted boards go to Trash (on paid plans) and can be restored via UI within 90 days after deletion.
-
delete-card-itemDestructive 4/5Delete a specific card item from a Miro board
-
delete-connectorDestructive 4/5Delete a specific connector from a Miro board
-
delete-document-itemDestructive 4/5Delete a specific document item from a Miro board
-
delete-embed-itemDestructive 4/5Delete a specific embed item from a Miro board
-
delete-frame-itemDestructive 4/5Delete a frame from a Miro board
-
delete-groupDestructive 4/5Delete a specific group from a Miro board
-
delete-image-itemDestructive 4/5Delete a specific image item from a Miro board
-
delete-itemDestructive 4/5Delete a specific item from a Miro board
-
delete-mindmap-nodeDestructive 4/5Delete a mind map node from a Miro board
-
delete-shape-itemDestructive 4/5Delete a specific shape item from a Miro board
-
delete-sticky-note-itemDestructive 4/5Delete a specific sticky note item from a Miro board
-
delete-tagDestructive 4/5Delete a specific tag from a Miro board
-
delete-text-itemDestructive 4/5Delete a specific text item from a Miro board
-
remove-board-memberDestructive 4/5Remove a specific member from a Miro board
-
remove-project-memberDestructive 4/5Removes a member from a project (Enterprise only)
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Miro Server
Enforce policy on Miro Server
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init