New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

glp_add_device

Add a device to the GLP workspace (async task, polls until complete, ~5min max).

SERVERAPI-Central SOURCEsecure-ssid/centralmcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of API-Central's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.