Inspect a container by name or ID.
AI agents call container_info to retrieve information from Podman MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Inspection operations are read-only; they retrieve configuration and state information about a container without modifying, executing, or deleting anything.
From the tool's definition 'Inspect a container by name or ID' — purely retrieves/queries container metadata with no side effects.
Attacks that exploit this kind of access
Inspect a container by name or ID. It is categorised as a Read tool in the Podman MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Podman MCP Server MCP server in PolicyLayer and add a rule for container_info: 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 Podman MCP Server. Nothing to install.
container_info 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 container_info 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 container_info. 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.
container_info is provided by the Podman MCP Server MCP server (kunwarmahen/podman-mcp-server). 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 →