AI agents call stage_delete to permanently remove resources in SingleStore MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes files or folders from SingleStore Stage storage. Deletion cannot be undone, making it a Destructive operation. The blast radius is high because unintended deletion of production data, notebooks, or job artifacts could cause significant data loss. Confidence is high because the function is explicit and unambiguous.
From the tool's definition Tool name is 'stage_delete' with description 'Delete a file or folder from Stage'. The verb 'Delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access stage_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SingleStore MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stage_delete:
{
"version": "1",
"default": "deny",
"hide": [
"stage_delete"
]
}stage_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a file or folder from Stage. It is categorised as a Destructive tool in the SingleStore MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SingleStore MCP Server MCP server in PolicyLayer and add a rule for stage_delete: 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 SingleStore MCP Server. Nothing to install.
stage_delete 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 stage_delete 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 stage_delete. 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.
stage_delete is provided by the SingleStore MCP Server MCP server (singlestore-labs/mcp-server-singlestore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 SingleStore MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 SingleStore MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.