flexsim_run · FlexSim MCP Server MCP: Risk & Policy

WHAT IT DOES

What flexsim_run does on FlexSim MCP Server

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

The tool executes a simulation engine with effects that cannot be predicted without knowing the model's configuration and parameters. While simulations are typically reversible via reset, the execution itself alters system state (time progression, resource consumption, model state changes) and could impact downstream decisions or resource allocation.

From the tool's definition Tool name 'flexsim_run' and description 'Start running the simulation continuously' indicate triggering external operations (simulation execution) whose side effects depend on model state and parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

flexsim_run Rate-limited

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

FAQ

Questions about flexsim_run

What does the flexsim_run tool do? +

Start running the simulation continuously. It is categorised as a Execute tool in the FlexSim 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 flexsim_run? +

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

What risk level is flexsim_run? +

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

Can I rate-limit flexsim_run? +

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

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

flexsim_run is provided by the FlexSim MCP Server MCP server (sethgame/mcp_flexsim). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.