Critical Risk →

manage_files

List, move, or delete files and folders. Paths starting with

How to control manage_files ↓

What manage_files does on Mediabox MCP

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

Critical Risk

Why manage_files needs a policy

The tool explicitly supports deleting files and folders, which is irreversible. While it also supports listing and moving (lower severity operations), the most severe applicable category is Destructive. Misuse by an AI agent could result in permanent data loss of media files across the server. The blast radius is critical given this is a media server managing potentially large libraries.

From the tool's definition 'List, move, or delete files and folders'

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

How to control manage_files

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

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

manage_files 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 Mediabox 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 manage_files

What does the manage_files tool do? +

List, move, or delete files and folders. Paths starting with. It is categorised as a Destructive tool in the Mediabox 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 manage_files? +

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

What risk level is manage_files? +

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

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

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

manage_files is provided by the Mediabox MCP server (juancmpdev/mediabox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mediabox MCP tool call.

Start from Mediabox 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.

30 Mediabox 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.