detect_communities
Run Leiden community detection on the file dependency graph. Identifies tightly-coupled file clusters (modules). Mutates the community index (stores results); idempotent. Deterministic — same
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/detect-communities.md
What detect_communities does on Trace
AI agents call detect_communities to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why detect_communities is rated Low
This tool performs static analysis on source code structure to identify module clusters. Although it stores results internally (community index), this is a side effect of analysis rather than user-facing data creation. The primary function is retrieving intelligence about code organization, making it a Read operation.
From the tool's definition detect_communities: 'Run Leiden community detection on the file dependency graph. Identifies tightly-coupled file clusters (modules).' The tool analyzes and retrieves structural information from the dependency graph.
Attacks that exploit this kind of access
The rule that runs detect_communities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_communities, this is the rule to start with:
detect_communities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every detect_communities call is checked against it from then on.
Questions about detect_communities
Run Leiden community detection on the file dependency graph. Identifies tightly-coupled file clusters (modules). Mutates the community index (stores results); idempotent. Deterministic — same. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for detect_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 Trace. Nothing to install.
detect_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 detect_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 detect_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.
detect_communities is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue