run_simulation · M/M/1 and M/M/c Queue Simulation Server MCP

WHAT IT DOES

What run_simulation does on M/M/1 and M/M/c Queue Simulation Server

AI agents invoke run_simulation to trigger actions in M/M/1 and M/M/c Queue Simulation 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_simulation needs a policy

This tool executes simulations (runs code/external operations) whose outputs depend on input parameters. It is not destructive (simulations don't delete data), not financial, and not merely a read operation. The empty description reduces confidence slightly, but the name and context strongly indicate Execute category.

From the tool's definition Tool name 'run_simulation' combined with sibling tools like 'run_mmc_simulation', 'run_mps_sim', and 'run_multiple_simulations' indicates code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_simulation Rate-limited

run_simulation 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_simulation": {
      "limits": [
        {
          "counter": "run_simulation_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 M/M/1 and M/M/c Queue Simulation Server, so you can run agents against it safely.

FAQ

Questions about run_simulation

What does the run_simulation tool do? +

run_simulation. It is categorised as a Execute tool in the M/M/1 and M/M/c Queue Simulation 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_simulation? +

Register the M/M/1 and M/M/c Queue Simulation Server MCP server in PolicyLayer and add a rule for run_simulation: 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 M/M/1 and M/M/c Queue Simulation Server. Nothing to install.

What risk level is run_simulation? +

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

Can I rate-limit run_simulation? +

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

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

run_simulation is provided by the M/M/1 and M/M/c Queue Simulation Server MCP server (kiyoung8/simulation_by_simpy_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.