Get detected code communities (clusters of tightly-coupled modules). Returns community IDs, member counts, cohesion scores, and labels.
AI agents call get_communities 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.
The tool queries and retrieves pre-computed codebase analysis data (community detection results) without performing any side effects, modifications, or code execution. This is a straightforward data retrieval operation consistent with the 'Read' category.
From the tool's definition Tool returns detected code communities with IDs, member counts, cohesion scores, and labels - purely informational retrieval with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_communities 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_communities:
{
"version": "1",
"default": "deny",
"tools": {
"get_communities": {}
}
}get_communities 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 detected code communities (clusters of tightly-coupled modules). Returns community IDs, member counts, cohesion scores, and labels. 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_communities: 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_communities 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_communities 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_communities. 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_communities 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.