AI agents call get_hierarchy to retrieve information from Synapse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the tool is deprecated/removed, if it were functional it would query and retrieve type hierarchy information from the FalkorDB graph—a pure read operation with no side effects, data modifications, code execution, or destructive capabilities. The severity is low because read operations on code structure pose minimal risk.
From the tool's definition Tool description states it is removed and recommends using 'get_context_for' instead. The implied functionality based on name and context (querying type hierarchy in a code graph database) is a read-only operation that retrieves structural information about…
Attacks that exploit this kind of access
This tool has been removed. Use get_context_for instead -- it includes type hierarchy in its output. It is categorised as a Read tool in the Synapse MCP Server, which means it retrieves data without modifying state.
Register the Synapse MCP server in PolicyLayer and add a rule for get_hierarchy: 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 Synapse. Nothing to install.
get_hierarchy 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_hierarchy 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_hierarchy. 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_hierarchy is provided by the Synapse MCP server (synappscodecomprehension/synapps). 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 →