agregar_habitacion
AI agents use agregar_habitacion to create or update resources in MCP Domotica Backend — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Domotica Backend environment.
The name 'agregar_habitacion' (add room) implies creating/writing a new room record in the system, which is a reversible write operation. However, the description is empty, which lowers confidence. Based on sibling tools context (smart home device management) and the 'agregar_' prefix (same as 'agregar_dispositivo' = add device), this is most likely a Write operation that creates a new room configuration.
From the tool's definition Tool name 'agregar_habitacion' translates from Spanish as 'add room', suggesting creation of a new room entity in the smart home system.
Attacks that exploit this kind of access
agregar_habitacion. It is categorised as a Write tool in the MCP Domotica Backend MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Domotica Backend MCP server in PolicyLayer and add a rule for agregar_habitacion: 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.
agregar_habitacion is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the agregar_habitacion 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 agregar_habitacion. 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.
agregar_habitacion 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 →