Find implementations of an interface or abstract class
AI agents call find_implementations to retrieve information from CodeGraphMCPServer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only code analysis tool. It searches the codebase to locate implementations of a given interface or abstract class, returning results for developer understanding. There are no side effects, no code execution, no data modifications, and no irreversible actions. The worst-case misuse would be information gathering, which has minimal blast radius in a code analysis context.
From the tool's definition Tool name 'find_implementations' and description 'Find implementations of an interface or abstract class' indicate a query/search operation that retrieves structural information from the codebase without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access find_implementations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeGraphMCPServer, and nothing reaches the server without passing your rules. This is the rule we recommend for find_implementations:
{
"version": "1",
"default": "deny",
"tools": {
"find_implementations": {}
}
}find_implementations 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 implementations of an interface or abstract class. It is categorised as a Read tool in the CodeGraphMCPServer MCP Server, which means it retrieves data without modifying state.
Register the CodeGraphMCPServer MCP server in PolicyLayer and add a rule for find_implementations: 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 CodeGraphMCPServer. Nothing to install.
find_implementations 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_implementations 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_implementations. 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_implementations is provided by the CodeGraphMCPServer MCP server (nahisaho/codegraphmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeGraphMCPServer, 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.
14 CodeGraphMCPServer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.