High Risk →

run_uv_script_remote

run_uv_script_remote

How to control run_uv_script_remote ↓

What run_uv_script_remote does on Union MCP

AI agents invoke run_uv_script_remote to trigger actions in Union MCP. 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.

High Risk

Why run_uv_script_remote needs a policy

This tool executes arbitrary UV (Python) scripts on a remote system, triggering external operations whose effects depend entirely on script content. While the description is missing (lowering confidence slightly), the name and sibling tools make the Execute classification clear.

From the tool's definition Tool name 'run_uv_script_remote' indicates execution of user-supplied scripts remotely. Related tools like 'build_uv_script_image_remote' and 'flyte_uv_script_example' confirm this is a remote code execution context.

Documented attack patterns abuse exactly the kind of access run_uv_script_remote gives an agent:

How to control run_uv_script_remote

PolicyLayer is an MCP gateway — it sits between your AI agents and Union MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_uv_script_remote:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_uv_script_remote": {
      "limits": [
        {
          "counter": "run_uv_script_remote_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

run_uv_script_remote 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.

  1. Create a free account and register Union MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about run_uv_script_remote

What does the run_uv_script_remote tool do? +

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

How do I enforce a policy on run_uv_script_remote? +

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

What risk level is run_uv_script_remote? +

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

Can I rate-limit run_uv_script_remote? +

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

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

run_uv_script_remote is provided by the Union MCP server (unionai-oss/union-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Union MCP tool call.

Start from Union MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 Union MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.