AI agents use addTodo to create or update resources in TypeSpec MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TypeSpec MCP Server environment.
This tool creates or modifies data (a new todo item) in a reversible manner—it can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move money. The low severity reflects the minimal blast radius: a spurious todo is trivial to remove.
From the tool's definition Tool name 'addTodo' and description 'Add a new todo' indicate creation of a new data record.
Documented attack patterns abuse exactly the kind of access addTodo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TypeSpec MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for addTodo:
{
"version": "1",
"default": "deny",
"tools": {
"addTodo": {
"limits": [
{
"counter": "addtodo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addTodo stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a new todo. It is categorised as a Write tool in the TypeSpec MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TypeSpec 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 TypeSpec 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 TypeSpec MCP Server MCP server (microsoft/typespec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TypeSpec MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 TypeSpec MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.