protect_update_chime
A write tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-update-chime.md
What protect_update_chime does on UniFi Access MCP
AI agents use protect_update_chime to create or update resources in UniFi Access MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UniFi Access MCP environment.
Why protect_update_chime is rated Medium
The 'update' verb indicates a Write operation (reversible modification). While the tool description is empty, the naming convention and server context (UniFi Access physical access control) suggest this modifies chime device settings. This is less severe than Execute (no arbitrary code/commands), not Destructive (changes are reversible), and not Financial.
From the tool's definition Tool name 'protect_update_chime' indicates modification of chime settings/configuration. Description is empty, limiting certainty. Context shows this server manages physical access control systems (doors, credentials, policies).
Attacks that exploit this kind of access
The rule that runs protect_update_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_update_chime, this is the rule to start with:
protect_update_chime stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every protect_update_chime call is checked against it from then on.
Questions about protect_update_chime
protect_update_chime is a write tool on the UniFi Access MCP server. It is categorised as a Write tool in the UniFi Access MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_update_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.
protect_update_chime is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the protect_update_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.
Set action: deny in the PolicyLayer policy for protect_update_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.
protect_update_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.
More on UniFi Access, and thousands of servers like it.
This server
Across the catalogue