Find frontend call sites (fetch/axios) that hit a given API route path — answers
AI agents call find_api_callers to retrieve information from Codebase Context 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 of a codebase to locate and retrieve information about where API calls originate from. It searches for call sites matching a given route pattern but does not execute code, modify files, delete data, or trigger external operations. The analysis is read-only introspection of the repository structure. Confidence is very high given the clear read-only nature of static code analysis.
From the tool's definition Tool name 'find_api_callers' and description 'Find frontend call sites (fetch/axios) that hit a given API route path' indicates static code search and retrieval.
Attacks that exploit this kind of access
Find frontend call sites (fetch/axios) that hit a given API route path — answers. It is categorised as a Read tool in the Codebase Context MCP Server, which means it retrieves data without modifying state.
Register the Codebase Context MCP server in PolicyLayer and add a rule for find_api_callers: 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 Codebase Context. Nothing to install.
find_api_callers 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_api_callers 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_api_callers. 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_api_callers is provided by the Codebase Context MCP server (oh-namgyu/codebase-context-mcp). 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 →