control_sprinkler_system · HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What control_sprinkler_system does on HC3 MCP Server

AI agents invoke control_sprinkler_system to trigger actions in HC3 MCP Server. 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 control_sprinkler_system needs a policy

This tool executes commands that trigger real-world effects (water flow control) whose consequences depend on execution parameters and timing. While not directly financial or destructive in the sense of data deletion, uncontrolled sprinkler activation could cause property damage, water waste, or system harm.

From the tool's definition Tool name 'control_sprinkler_system' with description stating it can 'start, stop, pause' the sprinkler system. These are direct operational commands that trigger external physical actions on hardware.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

control_sprinkler_system Rate-limited

control_sprinkler_system 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": {
    "control_sprinkler_system": {
      "limits": [
        {
          "counter": "control_sprinkler_system_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 HC3 MCP Server, so you can run agents against it safely.

FAQ

Questions about control_sprinkler_system

What does the control_sprinkler_system tool do? +

Control sprinkler system (start, stop, pause). It is categorised as a Execute tool in the HC3 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on control_sprinkler_system? +

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

What risk level is control_sprinkler_system? +

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

Can I rate-limit control_sprinkler_system? +

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

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

control_sprinkler_system is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.