Calculate centrality measures for entities in the knowledge graph. Returns betweenness, closeness, and degree centrality. These measures identify entities that bridge different parts of the graph, are close to all others, or have many connections.
AI agents call calculate_graph_centrality 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.
The tool performs analytical computations on graph structure to identify entity relationships and importance rankings. This is a passive analysis operation similar to search or query functionality—it retrieves derived insights from the knowledge graph but does not create, modify, or delete any data, nor does it execute code or trigger external operations. No side effects or irreversible actions are possible.
From the tool's definition Tool description states it 'Calculate[s] centrality measures' and 'Returns betweenness, closeness, and degree centrality.' These are read-only graph analysis operations that retrieve and compute metrics from existing knowledge graph data without modifying,…
Attacks that exploit this kind of access
Calculate centrality measures for entities in the knowledge graph. Returns betweenness, closeness, and degree centrality. These measures identify entities that bridge different parts of the graph, are close to all others, or have many connections. 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 calculate_graph_centrality: 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.
calculate_graph_centrality 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 calculate_graph_centrality 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 calculate_graph_centrality. 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.
calculate_graph_centrality 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 →