disarm_alarm_partition · HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What disarm_alarm_partition does on HC3 MCP Server

AI agents invoke disarm_alarm_partition 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 disarm_alarm_partition needs a policy

Disarming an alarm partition is an external operation with serious real-world security implications. It disables active security monitoring/protection in a physical space, which if misused by an AI agent could expose premises to intrusion or harm.

From the tool's definition 'Disarm alarm partition' — the tool disarms a security alarm system partition

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disarm_alarm_partition Rate-limited

disarm_alarm_partition 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": {
    "disarm_alarm_partition": {
      "limits": [
        {
          "counter": "disarm_alarm_partition_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 disarm_alarm_partition

What does the disarm_alarm_partition tool do? +

Disarm alarm partition. 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 disarm_alarm_partition? +

Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for disarm_alarm_partition: 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 disarm_alarm_partition? +

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

Can I rate-limit disarm_alarm_partition? +

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

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

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