Elimina un dispositivo del sistema.
AI agents call eliminar_dispositivo to permanently remove resources in MCP Domotica Backend — 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 device from the system. Removing a device could disrupt home automation rules, affect other dependent devices, and cannot be easily undone without re-adding and reconfiguring the device. This qualifies as Destructive with high severity given the potential blast radius across interconnected smart home systems.
From the tool's definition "Elimina un dispositivo del sistema" — 'Elimina' means 'deletes/removes' in Spanish; the tool removes a device from the system entirely.
Attacks that exploit this kind of access
Elimina un dispositivo del sistema. It is categorised as a Destructive tool in the MCP Domotica Backend MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Domotica Backend MCP server in PolicyLayer and add a rule for eliminar_dispositivo: 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 MCP Domotica Backend. Nothing to install.
eliminar_dispositivo 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 eliminar_dispositivo 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 eliminar_dispositivo. 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.
eliminar_dispositivo is provided by the MCP Domotica Backend MCP server (mcp-domotica/mcp-domotica-backend). 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 →