mega_rm

Remove files or folders from MEGA cloud storage

Accepts file system path (path)

Part of the Mega MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mega-mcp-server Destructive Risk 5/5

// WHEN AI AGENTS USE THIS TOOL

AI agents may call mega_rm to permanently remove or destroy resources in Mega. 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 MEGA_RM

Without a policy, an AI agent could call mega_rm in a loop, permanently destroying resources in Mega. 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.

io-github-expertvagabond-mega.yaml

tools:
  mega_rm:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mega policy for all 20 tools.

// DETAILS

Tool Name mega_rm

Category Destructive

MCP Server Mega MCP Server

Risk Level Critical

// MORE MEGA TOOLS

Write mega_export Write mega_import Write mega_mkdir Write mega_put Write mega_sync Read mega_cat Read mega_cd Read mega_cp

View all 20 tools →

// RELATED READING

// FAQ

What does the mega_rm tool do? +

Remove files or folders from MEGA cloud storage. It is categorised as a Destructive tool in the Mega 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 mega_rm? +

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

What risk level is mega_rm? +

mega_rm 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 mega_rm? +

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

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

mega_rm is provided by the Mega MCP server (mega-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

mega_rm

Enforce policies on Mega