Search across all project contexts for a keyword or phrase. Returns matching projects and modules with relevant snippets.
AI agents call search_context to retrieve information from Open Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data without any side effects. It does not create, modify, delete, execute code, or trigger external operations. The search operation is read-only and returns informational results only.
From the tool's definition Tool description states it 'Search[es] across all project contexts for a keyword or phrase' and 'Returns matching projects and modules with relevant snippets.' This is purely a query/search operation with no modification capability.
Attacks that exploit this kind of access
Search across all project contexts for a keyword or phrase. Returns matching projects and modules with relevant snippets. It is categorised as a Read tool in the Open Context MCP Server, which means it retrieves data without modifying state.
Register the Open Context 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 Open Context. Nothing to install.
search_context 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_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.
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.
search_context is provided by the Open Context MCP server (niawjunior/opencontext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →