Zaimに振替記録を作成します(口座間の資金移動)
AI agents use zaim_create_transfer to commit financial operations through Zaim API MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
zaim_create_transfer moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
Zaimに振替記録を作成します(口座間の資金移動). It is categorised as a Financial tool in the Zaim API MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Zaim API MCP Server MCP server in PolicyLayer and add a rule for zaim_create_transfer: 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_create_transfer is a Financial 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_create_transfer 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_create_transfer. 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_create_transfer 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.