unifi_configure_port_mirror
Configure port mirroring on a switch. Mirrors traffic from one port to a
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-configure-port-mirror.md
What unifi_configure_port_mirror does on UniFi Access MCP
AI agents invoke unifi_configure_port_mirror 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.
Why unifi_configure_port_mirror is rated High
Port mirroring is a network configuration operation that redirects all traffic from one switch port to another for monitoring/interception purposes. This is an Execute-level action as it triggers an external network operation with significant security implications — enabling traffic mirroring could expose sensitive data. The description appears truncated, lowering confidence slightly, but the intent is clear.
From the tool's definition Configure port mirroring on a switch. Mirrors traffic from one port to a
Attacks that exploit this kind of access
The rule that runs unifi_configure_port_mirror 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_configure_port_mirror, this is the rule to start with:
unifi_configure_port_mirror 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every unifi_configure_port_mirror call is checked against it from then on.
Questions about unifi_configure_port_mirror
Configure port mirroring on a switch. Mirrors traffic from one port to a. 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.
Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_configure_port_mirror: 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_configure_port_mirror is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unifi_configure_port_mirror 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_configure_port_mirror. 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_configure_port_mirror 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.
Across the catalogue