create_contam_case_variant · CONTAM MCP: Risk & Policy

WHAT IT DOES

What create_contam_case_variant does on CONTAM MCP

AI agents use create_contam_case_variant to create or update resources in CONTAM MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CONTAM MCP environment.

WHY IT NEEDS A POLICY

Why create_contam_case_variant needs a policy

This tool creates new data (cloned project folders and scenario variants) and modifies existing references reversibly. These are Write-category operations. The severity is medium rather than high because the modifications are scoped to project data within the CONTAM simulation environment and can be undone by deleting the created variants.

From the tool's definition The tool description explicitly states it will 'clone an existing CONTAM project folder into a named scenario folder and optionally update supported PRJ references.' Cloning and creating new project variants constitutes creation and modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_contam_case_variant Rate-limited

create_contam_case_variant stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_contam_case_variant": {
      "limits": [
        {
          "counter": "create_contam_case_variant_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 create_contam_case_variant

What does the create_contam_case_variant tool do? +

Use this when you need to clone an existing CONTAM project folder into a named scenario folder and optionally update supported PRJ references before running it. It is categorised as a Write tool in the CONTAM MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_contam_case_variant? +

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

create_contam_case_variant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_contam_case_variant? +

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

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

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