Find function calls that cross module boundaries
AI agents call find_cross_module_calls 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 retrieves and analyzes existing code relationships without modifying, executing, or deleting any code or data. It is a code analysis query tool that searches for patterns in module dependencies. Static analysis tools that query and report on code structure without side effects fall into the Read category, with low severity since the blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'find_cross_module_calls' and description 'Find function calls that cross module boundaries' indicate static analysis and querying of code structure. The verb 'find' is explicitly a Read operation.
Attacks that exploit this kind of access
Find function calls that cross module boundaries. 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 find_cross_module_calls: 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.
find_cross_module_calls 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 find_cross_module_calls 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 find_cross_module_calls. 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.
find_cross_module_calls 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 →