Use this when you want to initialize a CONTAM project through the official contamxpy bindings and read API-level zones, paths, AHS, contaminants, and control metadata.
AI agents call inspect_contamxpy_project to retrieve information from CONTAM MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries project metadata and configuration data through the contamxpy API bindings without modifying state, executing simulations, or triggering external operations. It is a read-only inspection operation with no side effects. The blast radius of misuse is minimal—an agent could only gain visibility into project structure and parameters.
From the tool's definition Tool description explicitly states "read API-level zones, paths, AHS, contaminants, and control metadata" and "initialize a CONTAM project".
Attacks that exploit this kind of access
Use this when you want to initialize a CONTAM project through the official contamxpy bindings and read API-level zones, paths, AHS, contaminants, and control metadata. It is categorised as a Read tool in the CONTAM MCP MCP Server, which means it retrieves data without modifying state.
Register the CONTAM MCP server in PolicyLayer and add a rule for inspect_contamxpy_project: 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.
inspect_contamxpy_project is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the inspect_contamxpy_project 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 inspect_contamxpy_project. 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.
inspect_contamxpy_project 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 →