Retrieves the imported dependencies and basic summary context for a specific, indexed file path.
AI agents call get_file_dependencies to retrieve information from Code Context Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs dependency analysis and metadata retrieval on already-indexed files. It returns information (dependencies and context) without creating, modifying, deleting, or executing anything. The most similar built-in tools on the server (read_file, list_directory_contents, search_code_context) are clearly Read operations, and get_file_dependencies operates in the same informational category.
From the tool's definition Tool retrieves imported dependencies and summary context for an indexed file - a read-only query operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Retrieves the imported dependencies and basic summary context for a specific, indexed file path. It is categorised as a Read tool in the Code Context Manager MCP Server, which means it retrieves data without modifying state.
Register the Code Context Manager MCP server in PolicyLayer and add a rule for get_file_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 Code Context Manager. Nothing to install.
get_file_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_file_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_file_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_file_dependencies is provided by the Code Context Manager MCP server (theraaz/code-context-manager-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 →