access_update_policy
A write tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/access-update-policy.md
What access_update_policy does on UniFi Access MCP
AI agents use access_update_policy 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 access_update_policy is rated Medium
The tool name strongly suggests it modifies access control policies, which is a Write operation. Updating access policies on a physical access control system could have significant security implications (e.g., granting or revoking access to physical spaces), warranting a high severity rating. However, confidence is lowered because the description is empty and the exact behavior is inferred solely from the tool name.
From the tool's definition Tool name 'access_update_policy' on a server managing 'doors, credentials, policies, visitors, and events'
Attacks that exploit this kind of access
The rule that runs access_update_policy 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 access_update_policy, this is the rule to start with:
access_update_policy 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 access_update_policy call is checked against it from then on.
Questions about access_update_policy
access_update_policy 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 access_update_policy: 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.
access_update_policy 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 access_update_policy 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 access_update_policy. 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.
access_update_policy 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