Find shared dependencies between two nodes (useful for debugging)
AI agents call gid_query_common_cause to retrieve information from GID MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a graph database to identify shared dependencies between nodes. It is a read-only operation that retrieves and analyzes existing data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an AI agent querying for non-existent dependencies or repeatedly running expensive queries might consume resources, but cannot harm data or trigger external operations.
From the tool's definition Tool description states 'Find shared dependencies between two nodes' with no modification or side effects. The phrase 'useful for debugging' indicates an informational/analytical purpose. The tool name includes 'query', which typically retrieves data.
Attacks that exploit this kind of access
Find shared dependencies between two nodes (useful for debugging). It is categorised as a Read tool in the GID MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GID MCP Server MCP server in PolicyLayer and add a rule for gid_query_common_cause: 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 GID MCP Server. Nothing to install.
gid_query_common_cause 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 gid_query_common_cause 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 gid_query_common_cause. 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.
gid_query_common_cause is provided by the GID MCP Server MCP server (potatouniverse/graph-indexed-development-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 →