Zaimの家計簿記録を削除します。削除は永続的で復元できません。
AI agents call zaim_delete_money_record to permanently remove resources in Zaim API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call zaim_delete_money_record doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Zaim API MCP Server is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Zaimの家計簿記録を削除します。削除は永続的で復元できません。. It is categorised as a Destructive tool in the Zaim API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zaim API MCP Server MCP server in PolicyLayer and add a rule for zaim_delete_money_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 Zaim API MCP Server. Nothing to install.
zaim_delete_money_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 zaim_delete_money_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 zaim_delete_money_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.
zaim_delete_money_record is provided by the Zaim API MCP Server MCP server (yone-k/zaim-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.