New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

scan_container_image

Scan a container image for HIGH and CRITICAL vulnerabilities using Trivy

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1999azzar-project-guardian-mcp-server/scan-container-image.md

What scan_container_image does on Project Guardian MCP

AI agents invoke scan_container_image to trigger actions in Project Guardian MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why scan_container_image is rated High

This tool executes an external security scanning tool (Trivy) against a container image. It triggers an external operation whose effects depend on the image argument provided.

From the tool's definition Scan a container image for HIGH and CRITICAL vulnerabilities using Trivy

Questions about scan_container_image

What does the scan_container_image tool do? +

Scan a container image for HIGH and CRITICAL vulnerabilities using Trivy. It is categorised as a Execute tool in the Project Guardian MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scan_container_image? +

Register the Project Guardian MCP server in PolicyLayer and add a rule for scan_container_image: 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 Project Guardian MCP. Nothing to install.

What risk level is scan_container_image? +

scan_container_image is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scan_container_image? +

Yes. Add a rate_limit block to the scan_container_image 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.

How do I block scan_container_image completely? +

Set action: deny in the PolicyLayer policy for scan_container_image. 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.

What MCP server provides scan_container_image? +

scan_container_image is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Project Guardian, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Project Guardian's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.