protect_alarm_get_status

Get the current arm status.

SERVERUniFi Access MCP SOURCEpypi:unifi-protect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-alarm-get-status.md

WHAT IT DOES

What protect_alarm_get_status does on UniFi Access MCP

AI agents call protect_alarm_get_status to retrieve information from UniFi Access MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why protect_alarm_get_status is rated Low

This tool retrieves alarm arm status information only, with no side effects, modifications, or actions triggered. It is a pure read operation analogous to checking system state. The low severity reflects that unauthorized access to alarm status alone poses minimal immediate risk compared to tools that could disarm systems or trigger actions.

From the tool's definition Tool name and description indicate 'Get the current arm status' — a query operation that retrieves state information without modifying or triggering any actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs protect_alarm_get_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UniFi Access MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For protect_alarm_get_status, this is the rule to start with:

protect_alarm_get_status Allowed

protect_alarm_get_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "protect_alarm_get_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every protect_alarm_get_status call is checked against it from then on.

FAQ

Questions about protect_alarm_get_status

What does the protect_alarm_get_status tool do? +

Get the current arm status. It is categorised as a Read tool in the UniFi Access MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on protect_alarm_get_status? +

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

What risk level is protect_alarm_get_status? +

protect_alarm_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit protect_alarm_get_status? +

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

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

protect_alarm_get_status is provided by the UniFi Access MCP server (pypi:unifi-protect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UniFi Access, and thousands of servers like it.

This server

All 272 UniFi Access tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →