Reset simulation to initial state (time = 0).
AI agents invoke flexsim_reset 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.
Resetting a simulation is an operational action that restarts the simulation state to time=0. While it doesn't delete files or move money, it is not a passive read—it actively triggers a state change in the running simulation environment. Any in-progress simulation run or unsaved intermediate state would be lost, making it more than a simple write but not fully destructive in the sense of permanent data deletion.
From the tool's definition Reset simulation to initial state (time = 0)
Attacks that exploit this kind of access
Reset simulation to initial state (time = 0). 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_reset: 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_reset 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_reset 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_reset. 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_reset 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.
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 →