execute_python

A execute tool on the Aos MCP server.

SERVERAos SOURCE@hybridlabor-api/aos

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/execute-python.md

WHAT IT DOES

What execute_python does on Aos

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

RISK

Why execute_python is rated High

Arbitrary Python execution in an Unreal Editor context can invoke destructive operations (delete_asset, delete_actors via siblings), modify game state, access filesystem, or trigger external commands. The blast radius is critical—an AI agent given this tool could cause severe damage to project assets and game logic.

From the tool's definition Tool named 'execute_python' with no description; context shows UEFN-TOOLBELT (Unreal Editor Fortnite tools) with sibling tools like 'batch_exec', 'delete_actors', 'delete_asset' indicating this server manages game asset/actor manipulation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs execute_python safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_python, this is the rule to start with:

execute_python Rate-limited

execute_python 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_python": {
      "limits": [
        {
          "counter": "execute_python_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every execute_python call is checked against it from then on.

FAQ

Questions about execute_python

What does the execute_python tool do? +

execute_python is a execute tool on the Aos MCP server. It is categorised as a Execute tool in the Aos 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_python? +

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

What risk level is execute_python? +

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

Can I rate-limit execute_python? +

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

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

execute_python is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →