ToDoを更新します
AI agents use update_todo to create or update resources in hokan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your hokan MCP Server environment.
This tool modifies existing to-do items but does not delete them or trigger financial transactions. Updates are generally reversible through subsequent updates or undo operations. Severity is medium because in an insurance CRM context, modifying task records could affect workflow management and customer communication if misused, but the impact is localized to task metadata rather than destructive or financial.
From the tool's definition Tool name 'update_todo' and description 'ToDoを更新します' (updates a to-do) indicate a reversible modification operation. The verb 'update' is explicitly a write operation.
Attacks that exploit this kind of access
ToDoを更新します. It is categorised as a Write tool in the hokan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the hokan MCP Server MCP server in PolicyLayer and add a rule for update_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 hokan MCP Server. Nothing to install.
update_todo 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 update_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 update_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.
update_todo is provided by the hokan MCP Server MCP server (shinonft/hokan-mcp). 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 →