Search the knowledge base using semantic/conceptual similarity (requires USE_SEMANTIC_SEARCH=1). Finds documents based on meaning, not just keywords. Example: searching for
AI agents call semantic_search to retrieve information from TDZ C64 Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
semantic_search is a query operation that retrieves and ranks documents by semantic similarity. It has no side effects—it neither modifies, deletes, executes code, nor transfers funds. The tool fits the Read category: it queries data and returns results.
From the tool's definition Tool description indicates 'Search the knowledge base using semantic/conceptual similarity' and 'Finds documents based on meaning, not just keywords.' The verb 'search' and the function of finding/retrieving documents without modification confirms read-only…
Attacks that exploit this kind of access
Search the knowledge base using semantic/conceptual similarity (requires USE_SEMANTIC_SEARCH=1). Finds documents based on meaning, not just keywords. Example: searching for. It is categorised as a Read tool in the TDZ C64 Knowledge MCP Server, which means it retrieves data without modifying state.
Register the TDZ C64 Knowledge 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 TDZ C64 Knowledge. 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 TDZ C64 Knowledge MCP server (michaeltroelsen/tdz-c64-knowledge). 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 →