Find documents similar to a given document. Uses semantic embeddings if available, falls back to TF-IDF. Great for discovering related content.
AI agents call find_similar 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.
This is a pure retrieval operation with no side effects. It queries existing document embeddings to surface semantically similar content, analogous to a search or filter operation. There is no data modification, deletion, execution of code, or financial impact. The low severity reflects minimal risk from accidental misuse—returning irrelevant search results causes no damage.
From the tool's definition Tool performs semantic search and similarity matching using embeddings and TF-IDF to 'find' and 'discover' documents.
Attacks that exploit this kind of access
Find documents similar to a given document. Uses semantic embeddings if available, falls back to TF-IDF. Great for discovering related content. 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 find_similar: 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.
find_similar 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 find_similar 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 find_similar. 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.
find_similar 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 →