kg_memory_connections
AI agents call kg_memory_connections to retrieve information from Metis Public Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name implies reading or querying relationships and connections from a knowledge graph structure. While the description is empty (lowering confidence), the naming convention and context within Metis (a research/citation tool emphasizing local data indexing) suggests this retrieves or explores stored memory connections rather than creating, modifying, or deleting them.
From the tool's definition Tool name 'kg_memory_connections' suggests querying or retrieving connections within a knowledge graph or memory system. The 'kg_' prefix indicates knowledge graph operations, and 'connections' suggests retrieval/traversal rather than modification.
Attacks that exploit this kind of access
kg_memory_connections. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for kg_memory_connections: 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 Metis Public Health. Nothing to install.
kg_memory_connections 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 kg_memory_connections 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 kg_memory_connections. 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.
kg_memory_connections is provided by the Metis Public Health MCP server (sveritg/metis_ph). 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 →