Hard-delete a todo permanently (removes from database). Free (0 credits).
AI agents call delete_todo to permanently remove resources in Jikan — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data that cannot be recovered. Hard-delete operations that remove records from a database are irreversible and fall under the Destructive category. While the blast radius is limited to todo items (not critical system data), the permanence and inability to undo the action justify 'high' severity. Confidence is high because the description is explicit about the destructive nature.
From the tool's definition Tool name 'delete_todo' combined with description 'Hard-delete a todo permanently (removes from database)' explicitly indicates irreversible deletion from persistent storage.
Attacks that exploit this kind of access
Hard-delete a todo permanently (removes from database). Free (0 credits). It is categorised as a Destructive tool in the Jikan MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jikan MCP server in PolicyLayer and add a rule for delete_todo: 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 Jikan. Nothing to install.
delete_todo 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_todo 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_todo. 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_todo is provided by the Jikan MCP server (thunderrabbit/jikan). 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 →