Get the most frequently called functions
AI agents call get_most_called_functions 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 a read-only query on static code analysis data. It retrieves metrics about function call patterns without creating, modifying, deleting, or executing any code. The broader FDEP MCP Server context (static code analysis for Haskell codebases) and sibling tools (analyze_*, build_*, execute_query) confirm this server's purpose is introspection and analysis.
From the tool's definition Tool is described as 'Get the most frequently called functions' — a retrieval operation that queries and returns static analysis data about function call frequencies. No modification, deletion, or execution of external code is implied.
Attacks that exploit this kind of access
Get the most frequently called functions. 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_most_called_functions: 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_most_called_functions 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_most_called_functions 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_most_called_functions. 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_most_called_functions 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 →