Get the most connected nodes (god nodes / architectural hubs) in the call graph. These are functions or classes with the highest number of call relationships.
AI agents call get_hub_nodes 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 queries and returns analytical data about code structure (call graph topology) without creating, modifying, deleting, executing commands, or making financial transactions. It is a straightforward read operation that retrieves pre-computed or analyzed metadata. The low severity reflects that misuse would only expose code architecture information, not cause operational harm.
From the tool's definition Tool 'get_hub_nodes' retrieves information about 'the most connected nodes' and 'functions or classes with the highest number of call relationships' from a call graph—a pure query/read operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_hub_nodes 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_hub_nodes:
{
"version": "1",
"default": "deny",
"tools": {
"get_hub_nodes": {}
}
}get_hub_nodes 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 the most connected nodes (god nodes / architectural hubs) in the call graph. These are functions or classes with the highest number of call relationships. 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_hub_nodes: 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_hub_nodes 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_hub_nodes 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_hub_nodes. 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_hub_nodes 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.