Search across project sources with smart intent detection. IMPORTANT:
AI agents call search_project 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.
This tool queries and retrieves project documentation and information without creating, modifying, deleting, or executing any operations. It is purely informational retrieval with smart routing to appropriate data sources. The highest risk is information disclosure of existing data, which is typical of Read operations and carries low severity.
From the tool's definition Tool name 'search_project' with description 'Search across project sources with smart intent detection' indicates a retrieval-only operation. No modification, deletion, code execution, or financial transaction is described or implied.
Documented attack patterns abuse exactly the kind of access search_project gives an agent:
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_project:
{
"version": "1",
"default": "deny",
"tools": {
"search_project": {}
}
} search_project 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 across project sources with smart intent detection. IMPORTANT:. It is categorised as a Read tool in the Project MCP MCP Server, which means it retrieves data without modifying state.
Register the Project MCP server in PolicyLayer and add a rule for search_project: 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.
search_project 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_project 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_project. 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_project 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.
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.