run_dynamic · ACM MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_dynamic does on ACM MCP Server

AI agents invoke run_dynamic 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_dynamic needs a policy

This tool executes a simulation—an external computational operation whose behavior and results depend on supplied arguments. It is not merely reading data (Read), creating/modifying reversible configuration (Write), or deleting data (Destructive). It runs a process that can consume computational resources and produce substantial outputs.

From the tool's definition Tool name 'run_dynamic' combined with description 'Run a dynamic simulation to the specified end time' indicates execution of a computational process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_dynamic Rate-limited

run_dynamic 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_dynamic": {
      "limits": [
        {
          "counter": "run_dynamic_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_dynamic

What does the run_dynamic tool do? +

Run a dynamic simulation to the specified end time (in simulation time units). 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_dynamic? +

Register the ACM MCP Server MCP server in PolicyLayer and add a rule for run_dynamic: 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_dynamic? +

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

Can I rate-limit run_dynamic? +

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

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

run_dynamic 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.