Add TODO to the DB
AI agents use addTodo to create or update resources in Remote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote MCP Server environment.
This tool creates new records in a database. It is a Write operation because it modifies data reversibly (todos can be deleted or updated later). Severity is medium because the blast radius depends on what an AI agent might add and how many records it creates; there is no authentication mentioned, increasing risk. Confidence is high because the name and description clearly indicate creation of database records.
From the tool's definition Tool name is 'addTodo' and description states 'Add TODO to the DB', indicating data creation/modification to a database.
Attacks that exploit this kind of access
Add TODO to the DB. It is categorised as a Write tool in the Remote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remote MCP Server MCP server in PolicyLayer and add a rule for addTodo: 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 Remote MCP Server. Nothing to install.
addTodo 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 addTodo 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 addTodo. 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.
addTodo is provided by the Remote MCP Server MCP server (yamanoku-playground/2025-06-03-todo-mcp-server). 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 →