Direct upstream nodes for a given node. Answers 'what does this need?'.
AI agents call get_dependencies 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.
This tool performs a traversal of a dependency graph to retrieve upstream dependencies for a given node. It retrieves existing information without modifying, deleting, executing external operations, or committing financial obligations. This is a straightforward read operation that queries graph structure.
From the tool's definition Tool name 'get_dependencies' and description 'Direct upstream nodes for a given node. Answers "what does this need?"' indicate a query operation that retrieves dependency information from a graph structure.
Attacks that exploit this kind of access
Direct upstream nodes for a given node. Answers 'what does this need?'. 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_dependencies: 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_dependencies 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_dependencies 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_dependencies. 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_dependencies 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 →