Delete a record from a PocketBase collection. This permanently removes the record and any associated files.
AI agents call delete_record to permanently remove resources in Ssakone Pocketbase — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data from a PocketBase collection, including associated files. This cannot be undone and represents a destructive operation. While the blast radius depends on what records an agent might target, the capability itself is inherently destructive.
From the tool's definition Tool description explicitly states "Delete a record" and "permanently removes the record and any associated files." The word "permanently" and "delete" are definitive indicators of irreversible data destruction.
Attacks that exploit this kind of access
Delete a record from a PocketBase collection. This permanently removes the record and any associated files. It is categorised as a Destructive tool in the Ssakone Pocketbase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ssakone Pocketbase MCP server in PolicyLayer and add a rule for delete_record: 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 Ssakone Pocketbase. Nothing to install.
delete_record 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 delete_record 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 delete_record. 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.
delete_record is provided by the Ssakone Pocketbase MCP server (@iflow-mcp/ssakone-pocketbase-mcp-server). 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 →