get_centrality
Calculate centrality metrics for entities in the graph
This record as markdown: /tools/danielsimonjr-memory-mcp/get-centrality.md
What get_centrality does on Enhanced Knowledge Graph Memory Server
AI agents call get_centrality to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_centrality is rated Low
This tool retrieves analytical metrics (centrality measures such as degree, betweenness, closeness, eigenvector centrality) from a knowledge graph. It performs read-only analysis with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; returning incorrect centrality scores does not compromise data integrity or trigger external actions.
From the tool's definition Tool name 'get_centrality' and description 'Calculate centrality metrics for entities in the graph' indicate a query operation that computes and retrieves graph analytics.
Attacks that exploit this kind of access
The rule that runs get_centrality safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_centrality, this is the rule to start with:
get_centrality is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every get_centrality call is checked against it from then on.
Questions about get_centrality
Calculate centrality metrics for entities in the graph. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for get_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 Enhanced Knowledge Graph Memory Server. Nothing to install.
get_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 get_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 get_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.
get_centrality is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue