Get class definitions with filtering by module or pattern
AI agents call list_classes 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 code analysis by listing and retrieving class definitions—a read-only operation with no side effects. Filtering by module or pattern is a query refinement, not a mutation. The FDEP server is explicitly described as providing 'static code analysis' for 'real-time queries,' confirming the tool's purpose is informational retrieval only.
From the tool's definition Tool name 'list_classes' and description 'Get class definitions with filtering by module or pattern' indicate a retrieval operation that queries and returns class definition data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get class definitions with filtering by module or pattern. 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 list_classes: 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.
list_classes 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 list_classes 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 list_classes. 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.
list_classes 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 →