AI agents use completeTodo to create or update resources in Todo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo environment.
An AI agent can call completeTodo faster than any human can review — one bad instruction and it creates or modifies resources in Todo by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Make the TODO complete. It is categorised as a Write tool in the Todo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todo MCP server in PolicyLayer and add a rule for completeTodo: 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 Todo. Nothing to install.
completeTodo 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 completeTodo 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 completeTodo. 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.
completeTodo is provided by the Todo MCP server (yusukebe/todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.