Low Risk

search_tasks

Search tasks by keyword in title, description, or content. Returns matching tasks with relevance ranking.

How to control search_tasks ↓

What search_tasks does on Project MCP

AI agents call search_tasks to retrieve information from Project MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_tasks needs a policy

This tool purely retrieves and searches existing task data based on keyword criteria. It has no side effects—no data is created, modified, deleted, or executed. The search operation is a standard read-only query operation, making it the lowest-severity category.

From the tool's definition Tool description states it 'Search tasks by keyword' and 'Returns matching tasks with relevance ranking.' These are query operations with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access search_tasks gives an agent:

How to control search_tasks

PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_tasks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_tasks": {}
  }
}

search_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Project MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_tasks

What does the search_tasks tool do? +

Search tasks by keyword in title, description, or content. Returns matching tasks with relevance ranking. It is categorised as a Read tool in the Project MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_tasks? +

Register the Project 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 Project MCP. Nothing to install.

What risk level is search_tasks? +

search_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_tasks? +

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.

How do I block search_tasks completely? +

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.

What MCP server provides search_tasks? +

search_tasks is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Project MCP tool call.

Start from Project MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.