High Risk →

create_execution

Trigger a Studio flow execution

Starts automated workflow

Part of the Twilio MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@twilio-labs/mcp Execute Risk 4/5

AI agents invoke create_execution to trigger processes or run actions in Twilio. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

create_execution can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

twilio.yaml
tools:
  create_execution:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Twilio policy for all 36 tools.

Tool Name create_execution
Category Execute
MCP Server Twilio MCP Server
Risk Level High

View all 36 tools →

Agents calling execute-class tools like create_execution have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

create_execution is one of the high-risk operations in Twilio. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the create_execution tool do? +

Trigger a Studio flow execution. It is categorised as a Execute tool in the Twilio MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_execution? +

Add a rule in your Intercept YAML policy under the tools section for create_execution. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Twilio MCP server.

What risk level is create_execution? +

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

Can I rate-limit create_execution? +

Yes. Add a rate_limit block to the create_execution rule in your Intercept 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 create_execution completely? +

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

create_execution is provided by the Twilio MCP server (@twilio-labs/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Twilio

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.