glp_add_device · API-Central MCP: Risk & Policy

WHAT IT DOES

What glp_add_device does on API-Central

AI agents use glp_add_device 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 glp_add_device needs a policy

This tool creates or modifies configuration by adding a device to a GreenLake Platform workspace. While the operation is reversible (devices can be removed), it commits infrastructure changes that affect network topology and management scope. The async nature and ~5min completion time suggest backend persistence.

From the tool's definition The tool description states it 'Add a device to the GLP workspace', which is a creation/addition operation. This is a reversible modification of system state (devices can be removed from workspaces).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

glp_add_device Rate-limited

glp_add_device 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": {
    "glp_add_device": {
      "limits": [
        {
          "counter": "glp_add_device_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 glp_add_device

What does the glp_add_device tool do? +

Add a device to the GLP workspace (async task, polls until complete, ~5min max). 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 glp_add_device? +

Register the API-Central MCP server in PolicyLayer and add a rule for glp_add_device: 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 glp_add_device? +

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

Can I rate-limit glp_add_device? +

Yes. Add a rate_limit block to the glp_add_device 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 glp_add_device completely? +

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

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