Get surprising cross-module connections in the codebase — edges that bridge structurally distant communities, cross execution surfaces, or involve weakly-resolved targets.
AI agents call get_surprises 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 retrieves and analyzes codebase metadata to identify structural connections. It performs no side effects, does not execute code, and does not modify data. It is a pure information retrieval operation analogous to grep or static analysis, consistent with the server's purpose of 'injecting the right code context' without modifying the codebase.
From the tool's definition Tool description states it 'Get[s] surprising cross-module connections' — a retrieval/query operation. The sibling tools (build_stack_tree, explain_flow, find_callees, find_callers) are all Read operations that analyze code structure without modification.
Documented attack patterns abuse exactly the kind of access get_surprises 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 get_surprises:
{
"version": "1",
"default": "deny",
"tools": {
"get_surprises": {}
}
}get_surprises 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.
Get surprising cross-module connections in the codebase — edges that bridge structurally distant communities, cross execution surfaces, or involve weakly-resolved targets. 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 get_surprises: 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.
get_surprises 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 get_surprises 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 get_surprises. 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.
get_surprises 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.