Find all classes that call a specific method
AI agents call find_classes_calling_method to retrieve information from CodeRAG 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 lookup on the Neo4J knowledge graph to identify code dependencies and call relationships. It has no side effects, does not execute code, and does not modify the codebase or graph structure. The query is informational only, making it a Read category tool with low severity.
From the tool's definition Tool name 'find_classes_calling_method' and description 'Find all classes that call a specific method' indicate a query/search operation that retrieves information about code relationships without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access find_classes_calling_method gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeRAG, and nothing reaches the server without passing your rules. This is the rule we recommend for find_classes_calling_method:
{
"version": "1",
"default": "deny",
"tools": {
"find_classes_calling_method": {}
}
} find_classes_calling_method is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find all classes that call a specific method. It is categorised as a Read tool in the CodeRAG MCP Server, which means it retrieves data without modifying state.
Register the CodeRAG MCP server in PolicyLayer and add a rule for find_classes_calling_method: 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 CodeRAG. Nothing to install.
find_classes_calling_method 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_classes_calling_method 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_classes_calling_method. 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_classes_calling_method is provided by the CodeRAG MCP server (jonnoc/coderag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeRAG, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 CodeRAG tools catalogued and risk-classified — across an index of 43,000+ MCP servers.