AI agents call get-todos to retrieve information from Todo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries todo data from the SQLite database without creating, modifying, or deleting records. The empty description lowers confidence slightly, but the name and server context clearly indicate a read-only list/query operation. No side effects or data mutations are implied. Severity is low because unauthorized reads of todo items pose minimal security risk compared to write/delete operations.
From the tool's definition Tool name 'get-todos' indicates retrieval operation; server description specifies 'list' as one of the supported operations, and this tool fits that pattern of querying todo items without modification.
Documented attack patterns abuse exactly the kind of access get-todos gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Todo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-todos:
{
"version": "1",
"default": "deny",
"tools": {
"get-todos": {}
}
}get-todos is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get-todos. It is categorised as a Read tool in the Todo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Todo MCP Server MCP server in PolicyLayer and add a rule for get-todos: 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 MCP Server. Nothing to install.
get-todos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-todos 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 get-todos. 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.
get-todos is provided by the Todo MCP Server MCP server (leonvanzyl/todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Todo 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.
3 Todo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.