dependencies
AI agents call dependencies to retrieve information from TempoGraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name 'dependencies' and the server's purpose as a code analysis engine, this most likely queries or retrieves dependency information (a read operation). The empty description reduces confidence slightly, but the tool follows typical patterns of code analysis tools that extract structural information. No evidence suggests it modifies, executes, or deletes code.
From the tool's definition Tool named 'dependencies' on a code graph context engine. No description provided, but naming convention and server context suggest it retrieves or lists code dependencies without modifying them.
Attacks that exploit this kind of access
dependencies. It is categorised as a Read tool in the TempoGraph MCP Server, which means it retrieves data without modifying state.
Register the TempoGraph MCP server in PolicyLayer and add a rule for 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 TempoGraph. Nothing to install.
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 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 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.
dependencies is provided by the TempoGraph MCP server (tempograph). 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 →