glp_archive_device

A destructive tool on the API-Central MCP server.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/glp-archive-device.md

WHAT IT DOES

What glp_archive_device does on API-Central

AI agents call glp_archive_device to permanently remove resources in API-Central, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why glp_archive_device is rated Critical

The word 'archive' in the context of device management typically implies removing a device from active management in a potentially irreversible way (archiving vs. deleting). On GreenLake Platform, archiving a device often decommissions it from the platform, which would be a destructive/irreversible operation. However, since the description is empty, confidence is reduced.

From the tool's definition Tool name: glp_archive_device. Description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs glp_archive_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_archive_device, this is the rule to start with:

glp_archive_device Hidden

glp_archive_device is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "glp_archive_device"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about glp_archive_device

What does the glp_archive_device tool do? +

glp_archive_device is a destructive tool on the API-Central MCP server. It is categorised as a Destructive tool in the API-Central MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on glp_archive_device? +

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

glp_archive_device is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit glp_archive_device? +

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

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

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

KEEP EXPLORING

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

This server

All 590 API-Central tools → Critical-risk tools on this server →

Across the catalogue

archive_purge on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →