start_contam_bridge_session · CONTAM MCP: Risk & Policy

WHAT IT DOES

What start_contam_bridge_session does on CONTAM MCP

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

This tool launches and controls an external simulation application (ContamX/CONTAM), which executes computational modeling of airflow and contaminant transport. While not destructive by itself, it initiates a process whose effects depend on how the agent configures and uses the subsequent bridge session.

From the tool's definition Tool description states 'launch ContamX in bridge mode and keep an interactive socket session open' — this initiates and maintains an external process (ContamX simulation software) whose behavior depends on subsequent configuration and commands passed through…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_contam_bridge_session Rate-limited

start_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": {
    "start_contam_bridge_session": {
      "limits": [
        {
          "counter": "start_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 start_contam_bridge_session

What does the start_contam_bridge_session tool do? +

Use this when you want to launch ContamX in bridge mode and keep an interactive socket session open across multiple MCP calls. 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 start_contam_bridge_session? +

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

start_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 start_contam_bridge_session? +

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

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

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