encender_horno · MCP Domotica Backend MCP: Risk & Policy

WHAT IT DOES

What encender_horno does on MCP Domotica Backend

AI agents invoke encender_horno to trigger actions in MCP Domotica Backend. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why encender_horno needs a policy

This tool triggers a real-world physical action: turning on a heating appliance (oven). While it is a 'write' to a smart home device state, activating an oven carries significant safety and physical risk (fire hazard, energy consumption, unattended appliance), making it an Execute action with high severity. Misuse by an AI agent could result in physical harm or property damage.

From the tool's definition 'Enciende el horno (activa el horno con la temperatura configurada)' — activates a physical oven appliance at a configured temperature

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

encender_horno Rate-limited

encender_horno stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "encender_horno": {
      "limits": [
        {
          "counter": "encender_horno_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Domotica Backend, so you can run agents against it safely.

FAQ

Questions about encender_horno

What does the encender_horno tool do? +

Enciende el horno (activa el horno con la temperatura configurada). It is categorised as a Execute tool in the MCP Domotica Backend MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on encender_horno? +

Register the MCP Domotica Backend MCP server in PolicyLayer and add a rule for encender_horno: 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.

What risk level is encender_horno? +

encender_horno is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit encender_horno? +

Yes. Add a rate_limit block to the encender_horno 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.

How do I block encender_horno completely? +

Set action: deny in the PolicyLayer policy for encender_horno. 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.

What MCP server provides encender_horno? +

encender_horno 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.