全面检查容器安全性
AI agents call check_container_security to retrieve information from ContainerGuard MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs security checks and analysis on containers, which are informational reads of container state and configuration rather than modifications, executions, or deletions. Security scanning/analysis tools typically query container properties, logs, and metadata to identify vulnerabilities without making changes. No evidence of command execution, data modification, or destructive operations.
From the tool's definition Tool name 'check_container_security' and description '全面检查容器安全性' (comprehensive check of container security) indicate a security analysis/monitoring function.
Attacks that exploit this kind of access
全面检查容器安全性. It is categorised as a Read tool in the ContainerGuard MCP MCP Server, which means it retrieves data without modifying state.
Register the ContainerGuard MCP server in PolicyLayer and add a rule for check_container_security: 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 ContainerGuard MCP. Nothing to install.
check_container_security 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 check_container_security 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 check_container_security. 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.
check_container_security is provided by the ContainerGuard MCP server (rockmelodies/containerguardmcp). 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 →