simulate · Clo3d MCP: Risk & Policy

WHAT IT DOES

What simulate does on Clo3d

AI agents invoke simulate to trigger actions in Clo3d. 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 simulate needs a policy

This tool executes a simulation process in CLO3D with externally-controlled parameters. While not destructive or financial, it triggers an external operation (cloth physics simulation) whose effects depend on arguments provided by the caller. The computational cost and potential to consume significant resources makes it Execute rather than Read.

From the tool's definition Tool name 'simulate' with description 'Run cloth simulation for the given number of frames' indicates execution of a computational operation with arguments (frame count) that can be varied.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulate Rate-limited

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

FAQ

Questions about simulate

What does the simulate tool do? +

Run cloth simulation for the given number of frames. It is categorised as a Execute tool in the Clo3d MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulate? +

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

What risk level is simulate? +

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

Can I rate-limit simulate? +

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

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

simulate is provided by the Clo3d MCP server (lilbonner/clo3d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.