Search and filter tasks by multiple criteria including text query, status, priority, tags, and project. Supports pagination and sorting.
AI agents call search_tasks to retrieve information from TasksMultiServer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_tasks performs querying and filtering of existing task data without any capability to create, modify, delete, or execute code. It returns results based on search criteria and pagination parameters. The operation is non-destructive and has no side effects beyond retrieving information. This is a classic Read operation with minimal blast radius—misuse would only expose task data the user already has access to.
From the tool's definition Tool description states: 'Search and filter tasks by multiple criteria including text query, status, priority, tags, and project.
Attacks that exploit this kind of access
Search and filter tasks by multiple criteria including text query, status, priority, tags, and project. Supports pagination and sorting. It is categorised as a Read tool in the TasksMultiServer MCP Server, which means it retrieves data without modifying state.
Register the TasksMultiServer MCP server in PolicyLayer and add a rule for search_tasks: 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 TasksMultiServer. Nothing to install.
search_tasks 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_tasks 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_tasks. 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_tasks is provided by the TasksMultiServer MCP server (keyurgolani/tasksmultiserver). 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 →