Search contexts by keyword or semantic query. Use personality_mode to re-rank results: historian (default), prophet (prediction-score ranked), archaeologist (least-recently-accessed first), minimalist (raw summaries).
AI agents call search_context to retrieve information from Semantic Context MCP 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 conversation context data without modifying, deleting, or executing external operations. The personality_mode parameter only affects result ranking/presentation, not data state. It falls squarely into the Read category with low severity since searching stored context has minimal blast radius—no side effects, no data destruction, no code execution, and no financial impact.
From the tool's definition Tool description states 'Search contexts by keyword or semantic query' with re-ranking options based on different modes.
Attacks that exploit this kind of access
Search contexts by keyword or semantic query. Use personality_mode to re-rank results: historian (default), prophet (prediction-score ranked), archaeologist (least-recently-accessed first), minimalist (raw summaries). It is categorised as a Read tool in the Semantic Context MCP MCP Server, which means it retrieves data without modifying state.
Register the Semantic 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 Semantic Context MCP. 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 Semantic Context MCP server (semanticintent/semantic-wake-intelligence-mcp). 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 →