Delete a user device by device ID
AI agents call delete_user_device to permanently remove resources in Red Bee MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a user device cannot be undone and permanently removes the device from the user's account, preventing further access or playback on that device. This is a classic destructive action that warrants high severity due to the potential impact on user access and account integrity.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a user device by device ID' — this is an irreversible removal operation.
Attacks that exploit this kind of access
Delete a user device by device ID. It is categorised as a Destructive tool in the Red Bee MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Red Bee MCP Server MCP server in PolicyLayer and add a rule for delete_user_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 Red Bee MCP Server. Nothing to install.
delete_user_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 delete_user_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 delete_user_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.
delete_user_device is provided by the Red Bee MCP Server MCP server (tamsi/redbee-mcp). 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 →