AI agents call list_knowledge_records to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing knowledge records with optional filtering. It performs no write, delete, or execution operations. The 'list' operation is a standard read-only query that has no side effects on the data being retrieved. Even in the context of a task management system, listing records is a fundamental retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'list_knowledge_records' and description states 'List local project knowledge records with optional filters' — uses the verb 'list' which retrieves/queries data without modification or side effects.
Attacks that exploit this kind of access
List local project knowledge records with optional filters. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for list_knowledge_records: 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 Todos. Nothing to install.
list_knowledge_records 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_knowledge_records 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_knowledge_records. 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_knowledge_records is provided by the Todos MCP server (@hasna/todos). 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 →