find_callers

Incrementally index the project, resolve the target symbol, and return indexed caller relationships.

SERVERACE-MCP SOURCE0215andrewfeng/ace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0215andrewfeng-ace-mcp/find-callers.md

WHAT IT DOES

What find_callers does on ACE-MCP

AI agents call find_callers to retrieve information from ACE-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_callers is rated Low

Tool retrieves caller relationships through code analysis without modifying or executing code.

From the tool's definition Incrementally index project, resolve target symbol, return indexed caller relationships.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_callers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ACE-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_callers, this is the rule to start with:

find_callers Allowed

find_callers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_callers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ACE-MCP, apply this rule, and every find_callers call is checked against it from then on.

FAQ

Questions about find_callers

What does the find_callers tool do? +

Incrementally index the project, resolve the target symbol, and return indexed caller relationships. It is categorised as a Read tool in the ACE-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_callers? +

Register the ACE MCP server in PolicyLayer and add a rule for find_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 ACE-MCP. Nothing to install.

What risk level is find_callers? +

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

Can I rate-limit find_callers? +

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

How do I block find_callers completely? +

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

What MCP server provides find_callers? +

find_callers is provided by the ACE MCP server (0215andrewfeng/ace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ACE, and thousands of servers like it.

This server

All 17 ACE tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →