Build a comprehensive type dependency graph showing relationships between types
AI agents call build_type_dependency_graph to retrieve information from FDEP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static code analysis to construct a read-only graph of type dependencies. It retrieves and organizes existing type relationship information from the codebase. No data is created, modified, deleted, or executed. Severity is low as misuse would at most expose architectural information about the codebase.
From the tool's definition 'Build a comprehensive type dependency graph showing relationships between types' — this is a static analysis/query operation that reads and visualizes type relationships without modifying any data.
Attacks that exploit this kind of access
Build a comprehensive type dependency graph showing relationships between types. It is categorised as a Read tool in the FDEP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FDEP MCP Server MCP server in PolicyLayer and add a rule for build_type_dependency_graph: 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 FDEP MCP Server. Nothing to install.
build_type_dependency_graph 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 build_type_dependency_graph 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 build_type_dependency_graph. 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.
build_type_dependency_graph is provided by the FDEP MCP Server MCP server (juspay/fdep-mcp-server). 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 →