Explain how two symbols are connected: directed paths, shared imports, and heritage (extends/implements). Returns up to 10 paths with at most 5 hops each.
AI agents call explain_relationship to retrieve information from code-intel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a code intelligence analysis tool that queries relationships between symbols and explains connections. It performs no write operations, does not execute arbitrary code, does not delete data, and does not involve financial transactions. It is purely informational retrieval about code structure, making it a Read category tool with low severity risk.
From the tool's definition Tool 'explain_relationship' retrieves and returns analysis of code connections (directed paths, shared imports, heritage) with no modification capability.
Attacks that exploit this kind of access
Explain how two symbols are connected: directed paths, shared imports, and heritage (extends/implements). Returns up to 10 paths with at most 5 hops each. It is categorised as a Read tool in the code-intel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the code-intel MCP Server MCP server in PolicyLayer and add a rule for explain_relationship: 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 code-intel MCP Server. Nothing to install.
explain_relationship 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 explain_relationship 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 explain_relationship. 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.
explain_relationship is provided by the code-intel MCP Server MCP server (vohongtho/code-intel-platform). 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 →