unifi_update_dynamic_dns
Update an existing Dynamic DNS entry.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-update-dynamic-dns.md
What unifi_update_dynamic_dns does on UniFi Access MCP
AI agents use unifi_update_dynamic_dns 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 unifi_update_dynamic_dns is rated Medium
This tool modifies existing DNS configuration, which is a reversible write operation. The severity is medium because misconfiguration could disrupt network connectivity and access to UniFi services, but the change itself is not destructive and can be corrected. In the context of a UniFi access control system, DNS updates could potentially redirect traffic but do not directly delete data or execute arbitrary code.
From the tool's definition Tool name contains 'update' and description states 'Update an existing Dynamic DNS entry,' indicating modification of configuration data. Dynamic DNS entries control network hostname resolution and routing.
Attacks that exploit this kind of access
The rule that runs unifi_update_dynamic_dns 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 unifi_update_dynamic_dns, this is the rule to start with:
unifi_update_dynamic_dns 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 unifi_update_dynamic_dns call is checked against it from then on.
Questions about unifi_update_dynamic_dns
Update an existing Dynamic DNS entry. 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 unifi_update_dynamic_dns: 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.
unifi_update_dynamic_dns 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 unifi_update_dynamic_dns 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 unifi_update_dynamic_dns. 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.
unifi_update_dynamic_dns 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