Find who calls a specific method in vanilla DayZ scripts (reverse call graph)
AI agents call find_callers to retrieve information from DayZ API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static analysis on existing DayZ script code to discover call relationships. It reads and searches through vanilla scripts to report callers of a method, analogous to 'find references' in an IDE. No code execution, modification, or data destruction occurs.
From the tool's definition Tool description states it 'Find[s] who calls a specific method in vanilla DayZ scripts (reverse call graph)'. This is a query/search operation that retrieves information about code relationships without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Find who calls a specific method in vanilla DayZ scripts (reverse call graph). It is categorised as a Read tool in the DayZ API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DayZ API MCP Server 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 DayZ API MCP Server. Nothing to install.
find_callers 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_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.
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.
find_callers is provided by the DayZ API MCP Server MCP server (quantumloader/dayz-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →