run_steady_state · ACM MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_steady_state does on ACM MCP Server

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

This tool executes a simulation with external effects—it triggers computational processes on the ACM system that cannot be predicted from arguments alone. While not destructive or financial, it performs a substantive operation ('run') whose outcomes depend on the current state of the simulation environment.

From the tool's definition Run a steady-state simulation. Returns convergence status and DOF.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_steady_state Rate-limited

run_steady_state 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_steady_state": {
      "limits": [
        {
          "counter": "run_steady_state_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 ACM MCP Server, so you can run agents against it safely.

FAQ

Questions about run_steady_state

What does the run_steady_state tool do? +

Run a steady-state simulation. Returns convergence status and DOF. It is categorised as a Execute tool in the ACM 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 run_steady_state? +

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

What risk level is run_steady_state? +

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

Can I rate-limit run_steady_state? +

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

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

run_steady_state is provided by the ACM MCP Server MCP server (pekosann/acm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.