Build a bidirectional call tree from a seed function/method. Shows callers (who invokes it) and callees (what it invokes).
AI agents call build_stack_tree to retrieve information from Reporecall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and analyzes existing code structure to display call relationships. It retrieves call graph data without modifying, executing, or deleting anything. Severity is low as misuse would only expose code structure information.
From the tool's definition Build a bidirectional call tree from a seed function/method. Shows callers (who invokes it) and callees (what it invokes).
Documented attack patterns abuse exactly the kind of access build_stack_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reporecall, and nothing reaches the server without passing your rules. This is the rule we recommend for build_stack_tree:
{
"version": "1",
"default": "deny",
"tools": {
"build_stack_tree": {}
}
}build_stack_tree 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.
Build a bidirectional call tree from a seed function/method. Shows callers (who invokes it) and callees (what it invokes). It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.
Register the Reporecall MCP server in PolicyLayer and add a rule for build_stack_tree: 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 Reporecall. Nothing to install.
build_stack_tree 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 build_stack_tree 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 build_stack_tree. 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.
build_stack_tree is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.