High Risk →

disable_coffee_machine

Temporarily sabotage the office coffee machine

How to control disable_coffee_machine ↓

AI agents invoke disable_coffee_machine to trigger actions in Hilanet MCP. 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.

High Risk

The tool 'executes' an action (sabotaging the coffee machine) that triggers an external operation or simulated state change. The word 'temporarily' suggests it is reversible, ruling out Destructive. Since this is a satirical/simulated MCP server, the real-world blast radius is likely low-to-none, but within the simulation context it could disrupt office operations.

From the tool's definition Temporarily sabotage the office coffee machine

Documented attack patterns abuse exactly the kind of access disable_coffee_machine gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Hilanet MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for disable_coffee_machine:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "disable_coffee_machine": {
      "limits": [
        {
          "counter": "disable_coffee_machine_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Hilanet MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the disable_coffee_machine tool do? +

Temporarily sabotage the office coffee machine. It is categorised as a Execute tool in the Hilanet MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on disable_coffee_machine? +

Register the Hilanet MCP server in PolicyLayer and add a rule for disable_coffee_machine: 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 Hilanet MCP. Nothing to install.

What risk level is disable_coffee_machine? +

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

Can I rate-limit disable_coffee_machine? +

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

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

disable_coffee_machine is provided by the Hilanet MCP server (adird/hilanet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hilanet MCP tool call.

Deterministic rules across all 12 Hilanet MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

12 Hilanet MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.