configurar_temporizador_horno · MCP Domotica Backend MCP

WHAT IT DOES

What configurar_temporizador_horno does on MCP Domotica Backend

AI agents use configurar_temporizador_horno 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.

WHY IT NEEDS A POLICY

Why configurar_temporizador_horno needs a policy

This tool sets/configures a timer on the oven, which is a reversible write operation modifying a device setting. It does not execute arbitrary code or irreversibly destroy data. However, misconfiguration of an oven timer could have physical safety implications, warranting a medium severity rating. Confidence is moderate due to the brief description providing limited detail.

From the tool's definition 'Configura el temporizador del horno' (Configures the oven timer)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configurar_temporizador_horno Rate-limited

configurar_temporizador_horno stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "configurar_temporizador_horno": {
      "limits": [
        {
          "counter": "configurar_temporizador_horno_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 configurar_temporizador_horno

What does the configurar_temporizador_horno tool do? +

Configura el temporizador del horno. 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.

How do I enforce a policy on configurar_temporizador_horno? +

Register the MCP Domotica Backend MCP server in PolicyLayer and add a rule for configurar_temporizador_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 configurar_temporizador_horno? +

configurar_temporizador_horno is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit configurar_temporizador_horno? +

Yes. Add a rate_limit block to the configurar_temporizador_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 configurar_temporizador_horno completely? +

Set action: deny in the PolicyLayer policy for configurar_temporizador_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 configurar_temporizador_horno? +

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