protect_trigger_chime

A execute tool on the UniFi Access MCP server.

SERVERUniFi Access MCP SOURCEpypi:unifi-protect-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-trigger-chime.md

WHAT IT DOES

What protect_trigger_chime does on UniFi Access MCP

AI agents invoke protect_trigger_chime to trigger actions in UniFi Access 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.

RISK

Why protect_trigger_chime is rated High

Triggering a chime is an Execute action—it causes an external device to perform an operation (produce sound) whose effects depend on context and cannot be trivially undone without causing some disruption. It's not Read (no data retrieval), Write (no data modification), Destructive (reversible), or Financial.

From the tool's definition Tool name 'protect_trigger_chime' suggests triggering an audio/chime output on physical security hardware. The empty description prevents full confirmation, but the name indicates activating a device action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs protect_trigger_chime 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_trigger_chime, this is the rule to start with:

protect_trigger_chime Rate-limited

protect_trigger_chime 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": {
    "protect_trigger_chime": {
      "limits": [
        {
          "counter": "protect_trigger_chime_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_trigger_chime call is checked against it from then on.

FAQ

Questions about protect_trigger_chime

What does the protect_trigger_chime tool do? +

protect_trigger_chime is a execute tool on the UniFi Access MCP server. It is categorised as a Execute tool in the UniFi Access 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 protect_trigger_chime? +

Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_trigger_chime: 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_trigger_chime? +

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

Can I rate-limit protect_trigger_chime? +

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

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

protect_trigger_chime 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 → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →