Inspect an individual Docker container.
AI agents call inspect_container to retrieve information from Universal Mcp Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs inspection or introspection of Docker container properties (status, configuration, environment, etc.), which is a read-only operation. While Docker containers can be sensitive systems, inspection alone does not execute commands within containers, modify container state, or cause destructive effects.
From the tool's definition Tool name 'inspect_container' and description 'Inspect an individual Docker container' indicate a query/retrieval operation that examines container metadata and state without modifying, executing code within, or deleting resources.
Attacks that exploit this kind of access
Inspect an individual Docker container. It is categorised as a Read tool in the Universal Mcp Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Universal Mcp Toolkit MCP server in PolicyLayer and add a rule for inspect_container: 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 Universal Mcp Toolkit. Nothing to install.
inspect_container 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_container 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_container. 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_container is provided by the Universal Mcp Toolkit MCP server (markgatcha/universal-mcp-toolkit). 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 →