Search todos by creation date (format: YYYY-MM-DD)
AI agents call search-todos-by-date 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.
This tool only searches and retrieves existing todo data based on a date filter. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It falls squarely within the Read category as a retrieval/query operation.
From the tool's definition Tool name 'search-todos-by-date' and description 'Search todos by creation date' indicate a query operation that retrieves filtered todo items without modifying, deleting, or executing any actions.
Documented attack patterns abuse exactly the kind of access search-todos-by-date 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 search-todos-by-date:
{
"version": "1",
"default": "deny",
"tools": {
"search-todos-by-date": {}
}
}search-todos-by-date 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.
Search todos by creation date (format: YYYY-MM-DD). It is categorised as a Read tool in the Todo List MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Todo List MCP Server MCP server in PolicyLayer and add a rule for search-todos-by-date: 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.
search-todos-by-date 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 search-todos-by-date 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 search-todos-by-date. 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.
search-todos-by-date 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.
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.