semantic_search
AI agents call semantic_search to retrieve information from MCP Local Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Semantic search queries local documentation indexes without modifying, deleting, or executing external operations. It retrieves matching documents based on semantic similarity. While the tool description is empty, the context of a RAG (Retrieval-Augmented Generation) system and peer tools strongly indicate this is a read-only search operation with no side effects.
From the tool's definition Tool name 'semantic_search' combined with server's stated RAG capabilities and sibling tools like 'search_local_docs', 'get_local_doc', and 'list_local_docs' all indicate retrieval operations.
Attacks that exploit this kind of access
semantic_search. It is categorised as a Read tool in the MCP Local Context MCP Server, which means it retrieves data without modifying state.
Register the MCP Local Context MCP server in PolicyLayer and add a rule for semantic_search: 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 MCP Local Context. Nothing to install.
semantic_search 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 semantic_search 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 semantic_search. 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.
semantic_search is provided by the MCP Local Context MCP server (steedmonteiro/mcp-local-context). 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 →