Delete a data file from a plugin's server-side storage.
AI agents call plugin_delete_data to permanently remove resources in Overlord MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of server-side data. Even though it's scoped to plugin storage rather than core system data, unauthorized or misdirected deletion could destroy configuration, state, or operational data that cannot be recovered. In the context of a C2 framework with 66+ tools, this represents a high-severity destructive capability.
From the tool's definition Tool name contains 'delete' and description states 'Delete a data file from a plugin's server-side storage' — this irreversibly removes data.
Attacks that exploit this kind of access
Delete a data file from a plugin's server-side storage. It is categorised as a Destructive tool in the Overlord MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Overlord MCP Server MCP server in PolicyLayer and add a rule for plugin_delete_data: 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 Overlord MCP Server. Nothing to install.
plugin_delete_data is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the plugin_delete_data 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.
Set action: deny in the PolicyLayer policy for plugin_delete_data. 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.
plugin_delete_data is provided by the Overlord MCP Server MCP server (skeeminator/overlord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →