list_service_groups
List every service group (full rows incl. ssl_proxy_domains) with each group's primary_agent + ordered agents[] from the service_group_agents join.
This record as markdown: /tools/dev-busymate-busymate-devtools/list-service-groups.md
What list_service_groups does on Busymate DevTools
AI agents call list_service_groups to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_service_groups is rated Low
This tool queries and returns service group configuration metadata without modifying, deleting, or executing any operations. It has no side effects and poses minimal risk to the system. The blast radius of misuse is limited to potential information disclosure about proxy configurations and service agents.
From the tool's definition Tool name is 'list_service_groups' and description states 'List every service group' with retrieval of configuration data (ssl_proxy_domains, primary_agent, agents).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_service_groups safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_service_groups, this is the rule to start with:
list_service_groups 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 Busymate DevTools, apply this rule, and every list_service_groups call is checked against it from then on.
Questions about list_service_groups
List every service group (full rows incl. ssl_proxy_domains) with each group's primary_agent + ordered agents[] from the service_group_agents join. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for list_service_groups: 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 Busymate DevTools. Nothing to install.
list_service_groups 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 list_service_groups 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 list_service_groups. 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.
list_service_groups is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue