AI agents call query_tasks_by_fields 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 is a query/search operation that retrieves task data based on filter criteria. It has no capability to modify, delete, or execute actions. The read-only nature and lack of side effects place it firmly in the Read category with low severity.
From the tool's definition Tool name is 'query_tasks_by_fields' and description states it 'Query tasks by local labels, priority, severity, owner, area, and custom fields' - these are retrieval operations with no data modification or side effects.
Attacks that exploit this kind of access
Query tasks by local labels, priority, severity, owner, area, and custom fields. 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 query_tasks_by_fields: 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.
query_tasks_by_fields 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 query_tasks_by_fields 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 query_tasks_by_fields. 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.
query_tasks_by_fields 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 →