Low Risk

find_callees

Find all functions called by an entity.

How to control find_callees ↓

What find_callees does on CodeGraphMCPServer

AI agents call find_callees 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.

Low Risk

Why find_callees needs a policy

This tool performs static code analysis to discover function call relationships, returning structural information about the codebase. It has no side effects, does not modify data, and does not execute arbitrary code or shell commands. It is purely informational, similar to other Read-category tools on the same server like 'get_code_snippet' and 'get_file_structure'.

From the tool's definition Tool name 'find_callees' and description 'Find all functions called by an entity' indicate a query operation that retrieves call graph information without modifying code or executing operations.

Documented attack patterns abuse exactly the kind of access find_callees gives an agent:

How to control find_callees

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_callees:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_callees": {}
  }
}

find_callees is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register CodeGraphMCPServer — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about find_callees

What does the find_callees tool do? +

Find all functions called by an entity. It is categorised as a Read tool in the CodeGraphMCPServer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_callees? +

Register the CodeGraphMCPServer MCP server in PolicyLayer and add a rule for find_callees: 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.

What risk level is find_callees? +

find_callees is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_callees? +

Yes. Add a rate_limit block to the find_callees 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.

How do I block find_callees completely? +

Set action: deny in the PolicyLayer policy for find_callees. 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.

What MCP server provides find_callees? +

find_callees 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.

Enforce policy on every CodeGraphMCPServer tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.