Cluster documents using K-Means algorithm on embeddings. Partitions documents into K clusters based on similarity.
AI agents call cluster_documents_kmeans 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.
K-Means clustering is a passive analytical operation. It computes similarity metrics and assigns documents to groups, producing insights without side effects. No data is created, modified, or destroyed; no external commands are executed; no financial transactions occur.
From the tool's definition The tool performs clustering analysis on document embeddings—a read-only operation that partitions and analyzes existing documents without creating, modifying, deleting, executing code, or moving money.
Attacks that exploit this kind of access
Cluster documents using K-Means algorithm on embeddings. Partitions documents into K clusters based on similarity. 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 cluster_documents_kmeans: 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.
cluster_documents_kmeans 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 cluster_documents_kmeans 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 cluster_documents_kmeans. 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.
cluster_documents_kmeans 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 →