search_context

Incrementally index the project and return code snippets relevant to a natural language, symbol, path, or semantic query, with optional context lines and path/language filters.

SERVERACE-MCP SOURCE0215andrewfeng/ace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0215andrewfeng-ace-mcp/search-context.md

WHAT IT DOES

What search_context does on ACE-MCP

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

RISK

Why search_context is rated Low

Tool retrieves and queries indexed code; no data modification, execution, or side effects.

From the tool's definition search code snippets, index project, query, retrieves relevant data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ACE-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_context, this is the rule to start with:

search_context Allowed

search_context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_context": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ACE-MCP, apply this rule, and every search_context call is checked against it from then on.

FAQ

Questions about search_context

What does the search_context tool do? +

Incrementally index the project and return code snippets relevant to a natural language, symbol, path, or semantic query, with optional context lines and path/language filters. It is categorised as a Read tool in the ACE-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_context? +

Register the ACE MCP server in PolicyLayer and add a rule for search_context: 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 ACE-MCP. Nothing to install.

What risk level is search_context? +

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

Can I rate-limit search_context? +

Yes. Add a rate_limit block to the search_context 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_context completely? +

Set action: deny in the PolicyLayer policy for search_context. 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_context? +

search_context is provided by the ACE MCP server (0215andrewfeng/ace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ACE, and thousands of servers like it.

This server

All 17 ACE tools →

Across the catalogue

binary_search on 010 Editor →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →