Get details for a specific community: files, inter-community dependencies. Read-only. Use after detect_communities to drill into a specific cluster. Returns JSON: { id, files, interCommunityDeps }.
AI agents call get_community to retrieve information from Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about code communities (clusters) and their dependencies without creating, modifying, or deleting data. It is purely informational, used after detect_communities to explore code structure analysis results. No mutations, executions, or destructive operations are possible.
From the tool's definition Tool description explicitly states 'Read-only' and returns structured metadata (id, files, interCommunityDeps). The verb 'Get details' and 'drill into' indicate retrieval operations with no side effects.
Documented attack patterns abuse exactly the kind of access get_community gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for get_community:
{
"version": "1",
"default": "deny",
"tools": {
"get_community": {}
}
}get_community 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 details for a specific community: files, inter-community dependencies. Read-only. Use after detect_communities to drill into a specific cluster. Returns JSON: { id, files, interCommunityDeps }. 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 get_community: 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.
get_community 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_community 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_community. 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_community 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.
Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.