get_service_group
Get one service group by id or name.
This record as markdown: /tools/dev-busymate-busymate-devtools/get-service-group.md
What get_service_group does on Busymate DevTools
AI agents call get_service_group 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | |
name | string | — |
Parameters from the server's own tool schema.
Why get_service_group is rated Low
This tool retrieves information about a service group. It takes an identifier (id or name) as input and returns data without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query with minimal security risk if misused by an AI agent—worst case is information disclosure of service group metadata.
From the tool's definition Tool name 'get_service_group' and description 'Get one service group by id or name' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_service_group 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 get_service_group, this is the rule to start with:
get_service_group 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 get_service_group call is checked against it from then on.
Questions about get_service_group
Get one service group by id or name. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
get_service_group accepts 2 parameters: id, name. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for get_service_group: 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.
get_service_group 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_service_group 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_service_group. 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_service_group 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