execute_state_transition · Qontinui MCP Server MCP

WHAT IT DOES

What execute_state_transition does on Qontinui MCP Server

AI agents invoke execute_state_transition to trigger actions in Qontinui 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.

WHY IT NEEDS A POLICY

Why execute_state_transition needs a policy

This tool triggers execution of state machine transitions, which are external operations whose effects depend on the transition ID argument. While not destructive by itself, executing arbitrary state transitions in a visual automation system controlling multiple displays poses high risk of unintended side effects (e.g., automating clicks, form submissions, or UI actions).

From the tool's definition Tool name contains 'execute' and description states it will 'Execute a specific transition by ID in the loaded state machine.' The server context indicates this is for 'visual automation workflows' that can affect 'multiple displays.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_state_transition Rate-limited

execute_state_transition 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_state_transition": {
      "limits": [
        {
          "counter": "execute_state_transition_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 Qontinui MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_state_transition

What does the execute_state_transition tool do? +

Execute a specific transition by ID in the loaded state machine. It is categorised as a Execute tool in the Qontinui MCP Server 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_state_transition? +

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

What risk level is execute_state_transition? +

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

Can I rate-limit execute_state_transition? +

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

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

execute_state_transition is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.