High Risk →

editor-run

[compact alias of run_project] Launches a Godot project in a new window and captures output. Use to test gameplay or verify script behavior. Runs until stop_project is called. Use get_debug_output to retrieve logs.

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

gopeak Execute Risk 3/5

AI agents invoke editor-run to trigger processes or run actions in Gopeak. 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.

editor-run 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.

io-github-had0yun-gopeak.yaml
tools:
  editor-run:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Gopeak policy for all 33 tools.

Tool Name editor-run
Category Execute
MCP Server Gopeak MCP Server
Risk Level High

View all 33 tools →

Agents calling execute-class tools like editor-run 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.

editor-run is one of the high-risk operations in Gopeak. 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 editor-run tool do? +

[compact alias of run_project] Launches a Godot project in a new window and captures output. Use to test gameplay or verify script behavior. Runs until stop_project is called. Use get_debug_output to retrieve logs.. It is categorised as a Execute tool in the Gopeak MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on editor-run? +

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

What risk level is editor-run? +

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

Can I rate-limit editor-run? +

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

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

editor-run is provided by the Gopeak MCP server (gopeak). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Gopeak

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.