add_devices_to_group · API-Central MCP: Risk & Policy

WHAT IT DOES

What add_devices_to_group does on API-Central

AI agents use add_devices_to_group to create or update resources in API-Central — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.

WHY IT NEEDS A POLICY

Why add_devices_to_group needs a policy

This tool creates or modifies data (device group assignments) in a reversible manner. While it affects network device organization and could have operational impact if misused (e.g., moving devices to inappropriate groups affecting policies or monitoring), the action is reversible by removing devices from groups. It does not execute arbitrary code, delete data permanently, or move money.

From the tool's definition 'Add devices to an existing device group' indicates modification of device group membership, which creates or changes organizational relationships in the network infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_devices_to_group Rate-limited

add_devices_to_group stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_devices_to_group": {
      "limits": [
        {
          "counter": "add_devices_to_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches API-Central, so you can run agents against it safely.

FAQ

Questions about add_devices_to_group

What does the add_devices_to_group tool do? +

Add devices to an existing device group by scope ID. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_devices_to_group? +

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

What risk level is add_devices_to_group? +

add_devices_to_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_devices_to_group? +

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

How do I block add_devices_to_group completely? +

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

What MCP server provides add_devices_to_group? +

add_devices_to_group 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.