Analyze how types are used throughout the codebase
AI agents call analyze_type_usage 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 by examining type usage patterns across a codebase. This is a non-destructive, side-effect-free read operation similar to grep, linting, or AST inspection. It retrieves and queries information about code structure but does not execute code, modify files, delete content, or trigger external operations.
From the tool's definition Tool name and description indicate data retrieval and analysis: 'Analyze how types are used throughout the codebase' performs querying and inspection of existing code structures without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Analyze how types are used throughout the codebase. 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 analyze_type_usage: 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.
analyze_type_usage 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 analyze_type_usage 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 analyze_type_usage. 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.
analyze_type_usage 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 →