Delete a vocab entry by my_id. Associated events are preserved but lose
AI agents call delete_emotion_vocab 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 performs an irreversible deletion of a vocabulary entry from the user's behavioral tracking system. Although associated events are preserved (mitigating complete data loss), the vocab entry itself cannot be recovered once deleted. This fits the Destructive category as it permanently removes data without undo capability.
From the tool's definition Tool name contains 'delete', description states 'Delete a vocab entry by my_id', indicating irreversible removal of data.
Attacks that exploit this kind of access
Delete a vocab entry by my_id. Associated events are preserved but lose. 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_emotion_vocab: 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_emotion_vocab 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_emotion_vocab 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_emotion_vocab. 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_emotion_vocab 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 →