Force client reconnect
AI agents invoke unifi_reconnect_client to trigger actions in UniFi MCP Server. 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.
This tool forces an external network operation (disconnecting and reconnecting a client) rather than simply reading or writing configuration data. It triggers an action with real-time effects on network connectivity. It is not destructive (data is not deleted) nor financial, making Execute the appropriate category. Misuse could disrupt legitimate users' connectivity, hence medium severity.
From the tool's definition 'Force client reconnect' — actively triggers a network reconnection operation on a connected client
Attacks that exploit this kind of access
Force client reconnect. It is categorised as a Execute tool in the UniFi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the UniFi MCP Server MCP server in PolicyLayer and add a rule for unifi_reconnect_client: 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 MCP Server. Nothing to install.
unifi_reconnect_client 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_reconnect_client 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_reconnect_client. 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_reconnect_client is provided by the UniFi MCP Server MCP server (mjrestivo16/mcp-unifi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →