run · OpenSimulator MCP Server MCP: Risk & Policy

WHAT IT DOES

What run does on OpenSimulator MCP Server

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

This tool enables execution of arbitrary commands against an OpenSimulator server infrastructure. While the actual severity depends on command choice, the tool itself provides no restrictions on what commands can be run. The most severe category applicable is Execute because the tool directly triggers external operations (console commands) whose effects depend entirely on arguments provided by the caller.

From the tool's definition Tool description states 'Run any raw OpenSimulator console command' which permits arbitrary command execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run Rate-limited

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

FAQ

Questions about run

What does the run tool do? +

Run any raw OpenSimulator console command. It is categorised as a Execute tool in the OpenSimulator 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 run? +

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

What risk level is run? +

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

Can I rate-limit run? +

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

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

run is provided by the OpenSimulator MCP Server MCP server (sanchorelaxo/opensim-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.