Delete an Alexa smart home group/room.
AI agents call alexa_delete_group to permanently remove resources in Alexa — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a smart home group/room configuration. Deletion cannot be undone without manual reconfiguration by the user. While not directly dangerous like data loss at scale, it destroys user-configured automation structures. This is more severe than Write (which is reversible) but less critical than Financial or widespread data destruction.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an Alexa smart home group/room.' The action removes a configured smart home grouping.
Attacks that exploit this kind of access
Delete an Alexa smart home group/room. It is categorised as a Destructive tool in the Alexa MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Alexa MCP server in PolicyLayer and add a rule for alexa_delete_group: 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 Alexa. Nothing to install.
alexa_delete_group 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 alexa_delete_group 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 alexa_delete_group. 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.
alexa_delete_group is provided by the Alexa MCP server (serversmx/alexa-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 →