create_app_run · Dust MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_app_run does on Dust MCP Server

AI agents invoke create_app_run to trigger actions in Dust 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 create_app_run needs a policy

The tool initiates execution of an application run, which is an active operation that triggers external computation or processes. Effects depend on the application being run and its arguments, making this an Execute category tool. Severity is high because misuse could trigger unintended application executions, consume resources, or cause unintended side effects depending on what the application does.

From the tool's definition "Start a new application run" - this triggers execution of an application/run process on the Dust platform

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_app_run Rate-limited

create_app_run 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": {
    "create_app_run": {
      "limits": [
        {
          "counter": "create_app_run_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 Dust MCP Server, so you can run agents against it safely.

FAQ

Questions about create_app_run

What does the create_app_run tool do? +

Start a new application run. It is categorised as a Execute tool in the Dust 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 create_app_run? +

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

What risk level is create_app_run? +

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

Can I rate-limit create_app_run? +

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

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

create_app_run is provided by the Dust MCP Server MCP server (ma3u/dust-mcp-server-postman-railway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.