kg_list_communities
List Louvain communities for an org (optionally scoped by project).
This record as markdown: /tools/io-stablebaseline-sb/kg-list-communities.md
What kg_list_communities does on Stable Baseline
AI agents call kg_list_communities to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
level | number | — | |
projectId | string | — |
Parameters from the server's own tool schema.
Why kg_list_communities is rated Low
This tool queries and returns information about community detection results in a Knowledge Graph. It performs no data modification, deletion, execution of external code, or financial operations. The 'list' verb and lack of any destructive or executable capability places it squarely in the Read category with low severity, as misuse would only expose information rather than cause damage or unwanted side effects.
From the tool's definition Tool name 'kg_list_communities' combined with description 'List Louvain communities' indicates a read-only query operation that retrieves/enumerates existing data structures (graph communities) without modification or side effects.
Attacks that exploit this kind of access
The rule that runs kg_list_communities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kg_list_communities, this is the rule to start with:
kg_list_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 Stable Baseline, apply this rule, and every kg_list_communities call is checked against it from then on.
Questions about kg_list_communities
List Louvain communities for an org (optionally scoped by project). It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
kg_list_communities accepts 2 parameters: level, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for kg_list_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 Stable Baseline. Nothing to install.
kg_list_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 kg_list_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 kg_list_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.
kg_list_communities is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue