list_device_groups

List all device groups (scopeId, scopeName, description).

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/list-device-groups.md

WHAT IT DOES

What list_device_groups does on API-Central

AI agents call list_device_groups to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_device_groups is rated Low

This tool retrieves and queries existing device group information without creating, modifying, or deleting any data. It is a straightforward read operation that poses minimal risk if called by an AI agent, as it only exposes existing configuration metadata.

From the tool's definition Tool name is 'list_device_groups' and description states it 'List all device groups' with metadata fields (scopeId, scopeName, description). The verb 'list' indicates data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_device_groups safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_device_groups, this is the rule to start with:

list_device_groups Allowed

list_device_groups is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_device_groups": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every list_device_groups call is checked against it from then on.

FAQ

Questions about list_device_groups

What does the list_device_groups tool do? +

List all device groups (scopeId, scopeName, description). It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_device_groups? +

Register the API-Central MCP server in PolicyLayer and add a rule for list_device_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 API-Central. Nothing to install.

What risk level is list_device_groups? +

list_device_groups is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_device_groups? +

Yes. Add a rate_limit block to the list_device_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.

How do I block list_device_groups completely? +

Set action: deny in the PolicyLayer policy for list_device_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.

What MCP server provides list_device_groups? +

list_device_groups is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →