delete_instance_file

Delete an uploaded file from a subscribed instance (Knowledge → Files). Removes the R2 object, its metadata, and its vectors.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/delete-instance-file.md

WHAT IT DOES

What delete_instance_file does on ProAgentStore

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

RISK

Why delete_instance_file is rated Critical

Irreversibly deletes file data, metadata, and vectors without undo capability.

From the tool's definition Delete an uploaded file, Removes the R2 object, removes metadata, removes vectors.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_instance_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_instance_file, this is the rule to start with:

delete_instance_file Hidden

delete_instance_file is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_instance_file"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every delete_instance_file call is checked against it from then on.

FAQ

Questions about delete_instance_file

What does the delete_instance_file tool do? +

Delete an uploaded file from a subscribed instance (Knowledge → Files). Removes the R2 object, its metadata, and its vectors. It is categorised as a Destructive tool in the ProAgentStore 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_instance_file? +

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

What risk level is delete_instance_file? +

delete_instance_file 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_instance_file? +

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

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

delete_instance_file is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools → Critical-risk tools on this server →

Across the catalogue

delete_file on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →