Direct downstream nodes for a given node. Answers 'what uses this?'.
AI agents call get_dependents to retrieve information from Procurement Graph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_dependents is a graph traversal query operation that retrieves relational information about dependencies without creating, modifying, deleting, or executing anything. It functions as a read-only navigation utility consistent with sibling tools like get_dependencies, get_analysis, and list_analyses. No blast radius from misuse since it only returns existing data.
From the tool's definition Tool answers 'what uses this?' by retrieving downstream dependency information from the graph. Description indicates pure querying/retrieval with no modification, execution, or deletion.
Attacks that exploit this kind of access
Direct downstream nodes for a given node. Answers 'what uses this?'. It is categorised as a Read tool in the Procurement Graph MCP Server, which means it retrieves data without modifying state.
Register the Procurement Graph MCP server in PolicyLayer and add a rule for get_dependents: 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 Procurement Graph. Nothing to install.
get_dependents 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_dependents 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_dependents. 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_dependents is provided by the Procurement Graph MCP server (mfbaig35r/procurement-graph). 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 →