Low Risk

get_callers

get_callers

How to control get_callers ↓

AI agents call get_callers to retrieve information from Srclight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves caller information from a code index—a query operation with no side effects. It navigates the call graph (mentioned in server description) to discover which functions/methods call a given symbol. No data is modified, deleted, or executed; it purely returns analytical results. The empty description lowers confidence slightly, but the name and sibling tools strongly suggest read-only intent.

From the tool's definition Tool name 'get_callers' combined with server purpose 'Deep code indexing' and sibling tools like 'find_pattern', 'find_imports', 'codebase_map', and 'blame_symbol' all indicate read-only analysis.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Srclight, and nothing reaches the server without passing your rules. This is the rule we recommend for get_callers:

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

get_callers 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 Srclight — 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.

Go deeper

What does the get_callers tool do? +

get_callers. It is categorised as a Read tool in the Srclight MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_callers? +

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

What risk level is get_callers? +

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

Can I rate-limit get_callers? +

Yes. Add a rate_limit block to the get_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 get_callers completely? +

Set action: deny in the PolicyLayer policy for get_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 get_callers? +

get_callers is provided by the Srclight MCP server (srclight/srclight). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Srclight tool call.

Deterministic rules across all 42 Srclight tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

42 Srclight tools catalogued and risk-classified — across an index of 42,500+ 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.