Explain the call flow around a query or function name. Resolves a seed symbol, builds a bidirectional call tree, and returns assembled flow context with callers, seed, and callees.
AI agents call explain_flow 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.
explain_flow queries and retrieves codebase information (call relationships, flow context) without creating, modifying, deleting, or executing operations. It is a pure read operation that gathers and assembles existing code intelligence. No side effects or irreversible actions are possible.
From the tool's definition Tool description states it 'Explain[s] the call flow', 'Resolves a seed symbol', 'builds a bidirectional call tree, and returns assembled flow context' — these are all retrieval and analysis operations with no modification of code or data.
Documented attack patterns abuse exactly the kind of access explain_flow 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 explain_flow:
{
"version": "1",
"default": "deny",
"tools": {
"explain_flow": {}
}
}explain_flow 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.
Explain the call flow around a query or function name. Resolves a seed symbol, builds a bidirectional call tree, and returns assembled flow context with callers, seed, and callees. 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 explain_flow: 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.
explain_flow 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 explain_flow 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 explain_flow. 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.
explain_flow 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.