ToDoを作成します
AI agents use create_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 creates a new to-do item, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or trigger uncontrolled external effects. The blast radius of misuse is limited to the creation of unnecessary task records that can be deleted. Severity is low because to-do items are administrative metadata with minimal business impact.
From the tool's definition Tool name 'create_todo' and description 'ToDoを作成します' (Creates a to-do) indicate creation of a task item. The sibling tools include destructive operations (delete_*) and data modifications, but this tool itself only creates reversible task records.
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 create_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.
create_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 create_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 create_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.
create_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 →