Search repository code with include/exclude patterns. Prompt-based wrapper.
AI agents call cursor_agent_search_repo to retrieve information from Cursor Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries code from a repository without side effects. No data is created, modified, deleted, or executed. It is a straightforward search utility that returns results matching specified patterns, fitting the 'Read' category with low severity since misuse would only result in unwanted information retrieval, not destructive or operational consequences.
From the tool's definition Tool performs code search within a repository using patterns. The name contains 'search' and description states 'Search repository code' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access cursor_agent_search_repo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cursor Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cursor_agent_search_repo:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_agent_search_repo": {}
}
} cursor_agent_search_repo 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 repository code with include/exclude patterns. Prompt-based wrapper. It is categorised as a Read tool in the Cursor Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor Agent MCP Server MCP server in PolicyLayer and add a rule for cursor_agent_search_repo: 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 Cursor Agent MCP Server. Nothing to install.
cursor_agent_search_repo 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 cursor_agent_search_repo 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 cursor_agent_search_repo. 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.
cursor_agent_search_repo is provided by the Cursor Agent MCP Server MCP server (sailay1996/cursor-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cursor Agent MCP Server, 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.
7 Cursor Agent MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.