access_update_device_config

A write tool on the UniFi Access MCP server.

SERVERUniFi Access MCP SOURCEpypi:unifi-protect-mcp

Medium RISK CLASS

Category Write

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/access-update-device-config.md

WHAT IT DOES

What access_update_device_config does on UniFi Access MCP

AI agents use access_update_device_config 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.

RISK

Why access_update_device_config is rated Medium

The 'update' verb indicates reversible modification of device configuration data. Without a description, confidence is moderate, but context shows this manages critical access control infrastructure (doors, credentials, policies). Misconfiguration could lock users out or compromise security but wouldn't permanently destroy data.

From the tool's definition Tool name contains 'update' which modifies configuration; part of UniFi Access system managing doors, credentials, and policies; sibling tools show this server controls physical access infrastructure.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

access_update_device_config Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "access_update_device_config": {
      "limits": [
        {
          "counter": "access_update_device_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about access_update_device_config

What does the access_update_device_config tool do? +

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

How do I enforce a policy on access_update_device_config? +

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

access_update_device_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit access_update_device_config? +

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

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

access_update_device_config 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →