Use this when you want a concise list of the names and ids available inside an active ContamX bridge session.
AI agents call list_contam_bridge_entities 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 existing entities within an active session and returns metadata (names and IDs). It has no side effects, does not execute code or simulations, does not modify data, and does not delete or move resources. The action is purely informational retrieval, fitting the 'Read' category with low severity.
From the tool's definition Tool description states it returns 'a concise list of the names and ids available inside an active ContamX bridge session' — a retrieval operation with no modification or execution of simulations.
Attacks that exploit this kind of access
Use this when you want a concise list of the names and ids available inside an active ContamX bridge session. 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 list_contam_bridge_entities: 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.
list_contam_bridge_entities 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 list_contam_bridge_entities 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 list_contam_bridge_entities. 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.
list_contam_bridge_entities 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 →