search_semantic
AI agents call search_semantic to retrieve information from TempoGraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_semantic' strongly suggests a read operation that searches or queries code semantically (likely via the 24 MCP tools on TempoGraph's code graph context engine). Without a description, confidence is moderate, but the semantic/search nomenclature aligns with query/retrieval patterns rather than write, execute, or destructive operations.
From the tool's definition Tool name 'search_semantic' indicates retrieval/query functionality on code graphs. No description provided, but semantic search typically queries code structure or meaning without modifying state.
Attacks that exploit this kind of access
search_semantic. It is categorised as a Read tool in the TempoGraph MCP Server, which means it retrieves data without modifying state.
Register the TempoGraph MCP server in PolicyLayer and add a rule for search_semantic: 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 TempoGraph. Nothing to install.
search_semantic 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_semantic 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_semantic. 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_semantic is provided by the TempoGraph MCP server (tempograph). 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 →