run_contamxpy_cosimulation · CONTAM MCP: Risk & Policy

WHAT IT DOES

What run_contamxpy_cosimulation does on CONTAM MCP

AI agents invoke run_contamxpy_cosimulation to trigger actions in CONTAM MCP. 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_contamxpy_cosimulation needs a policy

This is an Execute tool because it triggers external simulation operations (advancing PRJ models, applying adjustments) whose effects depend on provided arguments and cannot be trivially undone during a live co-simulation session.

From the tool's definition Tool enables 'advance a PRJ model step by step' and 'apply supported adjustments' to CONTAM simulation projects. 'run_contamxpy_cosimulation' executes external simulation steps with side effects dependent on the adjustments argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_contamxpy_cosimulation Rate-limited

run_contamxpy_cosimulation 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_contamxpy_cosimulation": {
      "limits": [
        {
          "counter": "run_contamxpy_cosimulation_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 CONTAM MCP, so you can run agents against it safely.

FAQ

Questions about run_contamxpy_cosimulation

What does the run_contamxpy_cosimulation tool do? +

Use this when you need paper-style ContamX API co-simulation: advance a PRJ model step by step, apply supported adjustments, and sample selected zone concentrations, flows, and control values. It is categorised as a Execute tool in the CONTAM MCP 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_contamxpy_cosimulation? +

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

What risk level is run_contamxpy_cosimulation? +

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

Can I rate-limit run_contamxpy_cosimulation? +

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

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

run_contamxpy_cosimulation is provided by the CONTAM MCP server (summer521521/contam_plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.