运行仿真
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.
This tool executes the FlexSim simulation engine. While simulations typically do not permanently destroy data, running a simulation can produce substantial computed effects that depend entirely on the model state and parameters—resource consumption, time advancement, state mutations within the simulation environment, and generation of results that may persist.
From the tool's definition Tool name 'flexsim_run' and description '运行仿真' (Chinese: 'run simulation') indicate execution of a simulation engine with potentially significant side effects.
Attacks that exploit this kind of access
运行仿真. 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.
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.
flexsim_run 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 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.
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.
flexsim_run is provided by the FlexSim MCP Server MCP server (quqbaku/flexsim-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →