Get detailed information about a specific module including function counts and statistics
AI agents call get_module_details 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.
This tool performs static analysis and information retrieval about code modules. It queries existing data (function counts, statistics) without side effects, code execution, or data modification. The FDEP server is explicitly described as providing 'static code analysis,' confirming a read-only analysis function. No destructive, execute, write, or financial operations are possible.
From the tool's definition Tool description states 'Get detailed information about a specific module including function counts and statistics' — retrieves module metadata without modifying code or executing arbitrary operations.
Attacks that exploit this kind of access
Get detailed information about a specific module including function counts and statistics. 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 get_module_details: 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.
get_module_details 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_module_details 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_module_details. 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_module_details 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 →