set · OpenSimulator MCP Server MCP: Risk & Policy

WHAT IT DOES

What set does on OpenSimulator MCP Server

AI agents invoke set 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 set needs a policy

The tool explicitly runs mutating and management commands against a virtual world server, including operations like restart (which disrupts service), set/change (which modifies server or region state), and save (which overwrites persisted data).

From the tool's definition "Run a mutating/management command (set/change/restart/save/etc.)" — covers a broad range of state-changing operations including restarts and saves

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set Rate-limited

set 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": {
    "set": {
      "limits": [
        {
          "counter": "set_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 set

What does the set tool do? +

Run a mutating/management command (set/change/restart/save/etc.). 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 set? +

Register the OpenSimulator MCP Server MCP server in PolicyLayer and add a rule for set: 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 set? +

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

Can I rate-limit set? +

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

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

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

// THE FULL RECORD

set is one line of OpenSimulator MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →