ALWAYS use this tool when asked about code organization, modules, coupling, or architecture structure. Detects functional communities — groups of code that frequently call each other. Returns clusters with cohesion scores, member counts, and internal/external edge ratios.
AI agents call nm_communities to retrieve information from NOMIK without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
nm_communities is a read-only analysis tool that queries the Neo4j knowledge graph to identify and return code structure metrics. It retrieves architectural insights (community detection, coupling analysis) without creating, modifying, deleting, or executing any code. The output is informational metadata about codebase organization. No side effects or irreversible actions are possible.
From the tool's definition Tool description states it 'Detects functional communities' and 'Returns clusters with cohesion scores, member counts, and internal/external edge ratios' — pure data retrieval and analysis operations with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access nm_communities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NOMIK, and nothing reaches the server without passing your rules. This is the rule we recommend for nm_communities:
{
"version": "1",
"default": "deny",
"tools": {
"nm_communities": {}
}
}nm_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.
ALWAYS use this tool when asked about code organization, modules, coupling, or architecture structure. Detects functional communities — groups of code that frequently call each other. Returns clusters with cohesion scores, member counts, and internal/external edge ratios. It is categorised as a Read tool in the NOMIK MCP Server, which means it retrieves data without modifying state.
Register the NOMIK MCP server in PolicyLayer and add a rule for nm_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 NOMIK. Nothing to install.
nm_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 nm_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 nm_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.
nm_communities is provided by the NOMIK MCP server (willfreed1/nomik). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NOMIK, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 NOMIK tools catalogued and risk-classified — across an index of 43,000+ MCP servers.