execute_action · Unifi MCP: Risk & Policy

WHAT IT DOES

What execute_action does on Unifi

AI agents invoke execute_action to trigger actions in Unifi. 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 IT NEEDS A POLICY

Why execute_action needs a policy

This tool triggers external operations (UniFi controller actions) whose effects are entirely dependent on the actionId and params provided. The generic nature of the params object means an AI agent could invoke arbitrary network management actions (restarting devices, changing configurations, disconnecting clients, modifying security settings, etc.).

From the tool's definition Tool name is 'execute_action' and description states 'Execute a UniFi action by actionId using a generic params object.' The verb 'execute' combined with 'generic params' indicates arbitrary action invocation without explicit constraints on what those actions…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_action Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_action": {
      "limits": [
        {
          "counter": "execute_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Unifi, so you can run agents against it safely.

FAQ

Questions about execute_action

What does the execute_action tool do? +

Execute a UniFi action by actionId using a generic params object. It is categorised as a Execute tool in the Unifi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_action? +

Register the Unifi MCP server in PolicyLayer and add a rule for execute_action: 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. Nothing to install.

What risk level is execute_action? +

execute_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_action? +

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

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

execute_action is provided by the Unifi MCP server (pproenca/unifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.