advance_contam_bridge_session · CONTAM MCP: Risk & Policy

WHAT IT DOES

What advance_contam_bridge_session does on CONTAM MCP

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

This tool actively sends control signals and weather adjustments to a live ContamX simulation session and can advance simulation time. These are external operations that modify the state of a running simulation process, making Execute the most appropriate category. Misuse could corrupt an ongoing simulation or produce invalid results used in engineering decisions, warranting high severity.

From the tool's definition 'send control/weather adjustments to a running bridge session and optionally advance ContamX to a new simulation time'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

advance_contam_bridge_session Rate-limited

advance_contam_bridge_session 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": {
    "advance_contam_bridge_session": {
      "limits": [
        {
          "counter": "advance_contam_bridge_session_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 advance_contam_bridge_session

What does the advance_contam_bridge_session tool do? +

Use this when you want to send control/weather adjustments to a running bridge session and optionally advance ContamX to a new simulation time. 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 advance_contam_bridge_session? +

Register the CONTAM MCP server in PolicyLayer and add a rule for advance_contam_bridge_session: 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 advance_contam_bridge_session? +

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

Can I rate-limit advance_contam_bridge_session? +

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

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

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