List todos with filtering options (by completion status, note, etc.)
AI agents call list_todos to retrieve information from Sidvy 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 and queries existing todo items with optional filters (completion status, note association, etc.). It has no side effects—it does not create, modify, delete, or execute operations. It falls squarely into the Read category as a safe data retrieval operation with minimal risk if misused by an agent.
From the tool's definition Tool is named 'list_todos' and described as listing todos with filtering options. The verb 'list' and the filtering/querying functionality indicate data retrieval without modification.
Attacks that exploit this kind of access
List todos with filtering options (by completion status, note, etc.). It is categorised as a Read tool in the Sidvy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for list_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 Sidvy MCP Server. Nothing to install.
list_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 list_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 list_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.
list_todos is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-mcp). 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 →