glp_add_device
Add a device to the GLP workspace (async task, polls until complete, ~5min max).
This record as markdown: /tools/secure-ssid-centralmcp/glp-add-device.md
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 glp_add_device is rated Medium
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
The rule that runs glp_add_device 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 glp_add_device, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every glp_add_device call is checked against it from then on.
Questions about glp_add_device
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.
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.
glp_add_device is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue