Low Risk

get-todo

Get a specific todo by ID

How to control get-todo ↓

AI agents call get-todo to retrieve information from Todo List MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves a single todo item by its identifier. It performs a read-only query without creating, modifying, deleting, or executing external operations. The minimal blast radius and lack of side effects justify a 'low' severity classification.

From the tool's definition Tool name 'get-todo' and description 'Get a specific todo by ID' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get-todo gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Todo List MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-todo:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-todo": {}
  }
}

get-todo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Todo List MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-todo tool do? +

Get a specific todo by ID. It is categorised as a Read tool in the Todo List MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-todo? +

Register the Todo List MCP Server MCP server in PolicyLayer and add a rule for get-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 Todo List MCP Server. Nothing to install.

What risk level is get-todo? +

get-todo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-todo? +

Yes. Add a rate_limit block to the get-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.

How do I block get-todo completely? +

Set action: deny in the PolicyLayer policy for get-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.

What MCP server provides get-todo? +

get-todo is provided by the Todo List MCP Server MCP server (regibyte/todo-list-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Todo List MCP Server tool call.

Deterministic rules across all 10 Todo List MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Todo List MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.