remove-project-member

// WHEN AI AGENTS USE THIS TOOL

AI agents may call remove-project-member to permanently remove or destroy resources in Miro Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON REMOVE-PROJECT-MEMBER

Without a policy, an AI agent could call remove-project-member in a loop, permanently destroying resources in Miro Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

k-jarzyna-mcp-miro.yaml

tools:
  remove-project-member:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Miro Server policy for all 97 tools.

// DETAILS

Tool Name remove-project-member

Category Destructive

MCP Server Miro Server MCP Server

Risk Level Critical

// MORE MIRO SERVER TOOLS

Destructive delete-app-card-item Destructive delete-board Destructive delete-card-item Destructive delete-connector Destructive delete-document-item Destructive delete-embed-item Destructive delete-frame-item Destructive delete-group

View all 97 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like remove-project-member have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete Agent Passport System — Cryptographic Identity for AI Agents remove_intent_card Agent Passport System — Cryptographic Identity for AI Agents revoke_delegation

// IN CONTEXT OF CRITICAL RISK

remove-project-member is one of the critical-risk operations in Miro Server. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the remove-project-member tool do? +

Removes a member from a project (Enterprise only). It is categorised as a Destructive tool in the Miro Server 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 remove-project-member? +

Add a rule in your Intercept YAML policy under the tools section for remove-project-member. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Miro Server MCP server.

What risk level is remove-project-member? +

remove-project-member 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 remove-project-member? +

Yes. Add a rate_limit block to the remove-project-member rule in your Intercept 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 remove-project-member completely? +

Set action: deny in the Intercept policy for remove-project-member. 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 remove-project-member? +

remove-project-member is provided by the Miro Server MCP server (k-jarzyna/mcp-miro). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Miro Server