Low Risk

search_context

Search for relevant context using semantic similarity

How to control search_context ↓

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

Low Risk

Even though search_context only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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

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

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

search_context 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 Gemini Context MCP Server — 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.

Go deeper

What does the search_context tool do? +

Search for relevant context using semantic similarity. It is categorised as a Read tool in the Gemini Context MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_context? +

Register the Gemini Context MCP Server 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 Gemini Context MCP Server. 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 Gemini Context MCP Server MCP server (ogoldberg/gemini-context-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gemini Context MCP Server tool call.

Deterministic rules across all 12 Gemini Context MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

12 Gemini Context MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.