Find code elements (functions, types, classes, imports) by source location
AI agents call find_element_by_location 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 information about code structure based on location parameters. It has no side effects—it does not execute code, modify source files, delete elements, or trigger external operations. It is a straightforward read operation consistent with static analysis tools that navigate and inspect codebase metadata.
From the tool's definition Tool description states it 'Find[s] code elements (functions, types, classes, imports) by source location' - a pure lookup/retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Find code elements (functions, types, classes, imports) by source location. 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_element_by_location: 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_element_by_location 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_element_by_location 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_element_by_location. 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_element_by_location 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 →