Archive a device in GLP (removes from Central, keeps in GLP inventory).
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.
Archiving a device removes it from Central, which is an irreversible removal from the active network management system. While the device remains in GLP inventory, the removal from Central cannot be undone without a separate re-provisioning action, making this effectively a destructive operation with high blast radius if misused on production network devices.
From the tool's definition Archive a device in GLP (removes from Central, keeps in GLP inventory)
Attacks that exploit this kind of access
Archive a device in GLP (removes from Central, keeps in GLP inventory). 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.
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.
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.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →