This record as markdown: /tools/aikogilpin-serac-agents/serac-delete.md
What serac_delete does on Serac
AI agents call serac_delete to permanently remove resources in Serac, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why serac_delete is rated Critical
The tool performs an irreversible deletion operation on stored data. Even though it operates on a single key rather than the entire namespace, deletion cannot be undone. Severity is high rather than critical because the blast radius is limited to the user's own namespace in a storage system, not shared infrastructure or financial systems.
From the tool's definition Tool name includes 'delete' and description states 'Delete a key from your namespace' — this irreversibly removes data.
Attacks that exploit this kind of access
The rule that runs serac_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For serac_delete, this is the rule to start with:
serac_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every serac_delete call is checked against it from then on.
Questions about serac_delete
Delete a key from your namespace. It is categorised as a Destructive tool in the Serac MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Serac MCP server in PolicyLayer and add a rule for serac_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 Serac. Nothing to install.
serac_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 serac_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 serac_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.
serac_delete is provided by the Serac MCP server (aikogilpin/serac-agents). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
Across the catalogue