AI agents invoke simulate to trigger actions in CLO3D 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.
This tool triggers an external computational operation (cloth physics simulation) whose outcome and duration depend on user-provided parameters. While not destructive (results can be undone/re-simulated) and not directly modifying saved data, it is an Execute action because it runs a complex algorithm with observable effects on the model state.
From the tool's definition Tool description states 'Run cloth simulation for a number of steps' — this directly executes a simulation operation with side effects (state changes in the 3D model) that depend on the argument (number of steps).
Documented attack patterns abuse exactly the kind of access simulate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CLO3D MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for simulate:
{
"version": "1",
"default": "deny",
"tools": {
"simulate": {
"limits": [
{
"counter": "simulate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Run cloth simulation for a number of steps. It is categorised as a Execute tool in the CLO3D MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CLO3D MCP Server 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 MCP Server. Nothing to install.
simulate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
simulate is provided by the CLO3D MCP Server MCP server (ubani-studio/clo3d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CLO3D MCP Server, 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.
33 CLO3D MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.