Use this when you need to create multiple named CONTAM scenario folders from one baseline PRJ and optionally run each scenario sequentially.
AI agents invoke run_contam_case_matrix 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.
This tool triggers automated sequential execution of CONTAM simulations across multiple scenarios. While it creates folders (Write-like), the primary function is simulation execution (Execute category).
From the tool's definition Tool creates multiple scenario folders from a baseline project and runs simulations sequentially. Creating folders and executing simulations represent code/process execution with side effects that depend on arguments (scenario names, baseline project,…
Attacks that exploit this kind of access
Use this when you need to create multiple named CONTAM scenario folders from one baseline PRJ and optionally run each scenario sequentially. 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.
Register the CONTAM MCP server in PolicyLayer and add a rule for run_contam_case_matrix: 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.
run_contam_case_matrix is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_contam_case_matrix 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.
Set action: deny in the PolicyLayer policy for run_contam_case_matrix. 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.
run_contam_case_matrix 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →