get_relationships
AI agents call get_relationships to retrieve information from Understand-Anything MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves relationship data from a code knowledge graph without modifying, executing, or deleting anything. It follows the pattern of other introspection tools on the server (get_layer_info, get_node_detail, get_graph_stats). Empty description slightly reduces confidence, but tool name and server purpose clearly indicate a query/retrieval operation with no side effects.
From the tool's definition Tool name 'get_relationships' with context of Knowledge Graph queries (find_path, get_class_hierarchy, get_node_detail) indicates data retrieval. Description is empty, but sibling tools are all read-only graph queries.
Attacks that exploit this kind of access
get_relationships. It is categorised as a Read tool in the Understand-Anything MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Understand-Anything MCP Server MCP server in PolicyLayer and add a rule for get_relationships: 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 Understand-Anything MCP Server. Nothing to install.
get_relationships 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_relationships 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_relationships. 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_relationships is provided by the Understand-Anything MCP Server MCP server (viethoangnguyenle/understand-anything-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 →