ajustar_horno
AI agents invoke ajustar_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.
The description is empty, lowering confidence. Based on the tool name 'ajustar_horno' (Spanish for 'adjust oven') and the server context supporting oven control, this likely adjusts oven settings (temperature, mode). Sibling tools like 'apagar_horno' (turn off oven) and 'configurar_temporizador_horno' (configure oven timer) confirm oven management capabilities.
From the tool's definition Tool name 'ajustar_horno' (adjust oven) on a smart home server that 'Supports lights, thermostats, fans, and ovens'
Attacks that exploit this kind of access
ajustar_horno. 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.
Register the MCP Domotica Backend MCP server in PolicyLayer and add a rule for ajustar_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.
ajustar_horno is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ajustar_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.
Set action: deny in the PolicyLayer policy for ajustar_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.
ajustar_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.
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 →