update_contam_project_references · CONTAM MCP: Risk & Policy

WHAT IT DOES

What update_contam_project_references does on CONTAM MCP

AI agents use update_contam_project_references 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 update_contam_project_references needs a policy

The tool creates or modifies data reversibly by updating project references within a CONTAM project file. While it changes configuration data that affects simulations, these changes are not irreversible (the previous state can be restored or reverted), and the tool does not delete data or execute arbitrary code.

From the tool's definition Tool description states it enables editing of referenced files inside a CONTAM .prj file: 'edit the referenced weather, contaminant, or library files inside a CONTAM .prj file.' This modifies project configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_contam_project_references Rate-limited

update_contam_project_references 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": {
    "update_contam_project_references": {
      "limits": [
        {
          "counter": "update_contam_project_references_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 update_contam_project_references

What does the update_contam_project_references tool do? +

Use this when you need to edit the referenced weather, contaminant, or library files inside a CONTAM .prj file. 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 update_contam_project_references? +

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

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

Can I rate-limit update_contam_project_references? +

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

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

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