Critical Risk →

delete_miro_board

Delete a Miro board (use with caution!)

How to control delete_miro_board ↓

What delete_miro_board does on Learning Hour MCP

AI agents call delete_miro_board to permanently remove resources in Learning Hour MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_miro_board needs a policy

This tool irreversibly deletes a Miro board, which cannot be undone. The caution warning in the description reinforces that this is a destructive action with potential significant impact. While the blast radius is scoped to a single board, deletion of collaborative content represents a serious destructive capability that warrants high severity.

From the tool's definition Tool name is 'delete_miro_board' and description states 'Delete a Miro board (use with caution!)'. The word 'Delete' combined with the caution warning explicitly indicates irreversible removal of data.

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

How to control delete_miro_board

PolicyLayer is an MCP gateway — it sits between your AI agents and Learning Hour MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_miro_board:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_miro_board"
  ]
}

delete_miro_board disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Learning Hour MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_miro_board

What does the delete_miro_board tool do? +

Delete a Miro board (use with caution!). It is categorised as a Destructive tool in the Learning Hour MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_miro_board? +

Register the Learning Hour MCP server in PolicyLayer and add a rule for delete_miro_board: 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 Learning Hour MCP. Nothing to install.

What risk level is delete_miro_board? +

delete_miro_board is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_miro_board? +

Yes. Add a rate_limit block to the delete_miro_board 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 delete_miro_board completely? +

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

delete_miro_board is provided by the Learning Hour MCP server (sdiamante13/learning-hour-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Learning Hour MCP tool call.

Start from Learning Hour MCP, 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.

8 Learning Hour MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.