Get statistics about the current cardiology knowledge graph.
AI agents call get_graph_stats to retrieve information from Cardiology Knowledge Graph MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns summary statistics about the knowledge graph structure without creating, modifying, or deleting any data. It is a read-only operation analogous to a SELECT COUNT or metadata inspection query.
From the tool's definition Tool name 'get_graph_stats' and description 'Get statistics about the current cardiology knowledge graph' indicate retrieval of aggregate information with no modification or side effects.
Attacks that exploit this kind of access
Get statistics about the current cardiology knowledge graph. It is categorised as a Read tool in the Cardiology Knowledge Graph MCP MCP Server, which means it retrieves data without modifying state.
Register the Cardiology Knowledge Graph MCP server in PolicyLayer and add a rule for get_graph_stats: 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 Cardiology Knowledge Graph MCP. Nothing to install.
get_graph_stats 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_graph_stats 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_graph_stats. 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_graph_stats is provided by the Cardiology Knowledge Graph MCP server (ryoureddy/cardiology-knowledge-graph-mcp). 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 →