Zaimの既存の家計簿記録を更新します
AI agents use zaim_update_money_record to create or update resources in Zaim API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zaim API MCP Server environment.
An AI agent can call zaim_update_money_record faster than any human can review — one bad instruction and it creates or modifies resources in Zaim API MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Zaimの既存の家計簿記録を更新します. It is categorised as a Write tool in the Zaim API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zaim API MCP Server MCP server in PolicyLayer and add a rule for zaim_update_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_update_money_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zaim_update_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_update_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_update_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.