Delete a device.
AI agents call deletedevice to permanently remove resources in Revel Digital MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of a device from the Revel Digital signage system. Deletion operations that cannot be undone are categorized as Destructive. The severity is high rather than critical because the impact is scoped to a single device rather than affecting financial systems or causing cascading infrastructure failure, though in a production environment this could be severe depending on device…
From the tool's definition Tool name is 'deletedevice' and description states 'Delete a device.' This is an irreversible deletion operation that removes digital signage infrastructure.
Attacks that exploit this kind of access
Delete a device. It is categorised as a Destructive tool in the Revel Digital MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Revel Digital MCP Server MCP server in PolicyLayer and add a rule for deletedevice: 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 Revel Digital MCP Server. Nothing to install.
deletedevice 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 deletedevice 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 deletedevice. 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.
deletedevice is provided by the Revel Digital MCP Server MCP server (reveldigital/reveldigital-mcp-server). 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 →