Use this when you need to confirm where CONTAM is installed and which executables this MCP server can access.
AI agents call discover_contam_installation 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 queries the system to retrieve installation paths and available executables. It performs no side effects, does not execute code or simulations, does not modify data, and does not delete or move resources. It is a straightforward discovery/inspection capability, analogous to a 'get' or 'list' operation.
From the tool's definition Tool name 'discover_contam_installation' and description state it is used to 'confirm where CONTAM is installed and which executables this MCP server can access' — a pure information retrieval operation with no modification, deletion, or execution of external…
Attacks that exploit this kind of access
Use this when you need to confirm where CONTAM is installed and which executables this MCP server can access. 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 discover_contam_installation: 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.
discover_contam_installation 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 discover_contam_installation 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 discover_contam_installation. 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.
discover_contam_installation 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 →