scan_unique_images
Scan all images used across page sources, global sources, and global sections. Returns a unique list of image URLs with which elements use each one. Useful for: image audit, finding broken/duplicated CDN URLs, bulk replace planning, theme migration. Scans every string field in the source tree (co...
This record as markdown: /tools/webcake-storefront/scan-unique-images.md
What scan_unique_images does on Webcake Storefront
AI agents call scan_unique_images to retrieve information from Webcake Storefront without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scan_unique_images is rated Low
This tool only reads and aggregates data about existing images across the storefront without altering, creating, or deleting any content. The blast radius of misuse is minimal — an attacker gains visibility into image asset usage but cannot modify storefront configuration, execute commands, or cause data loss. This is a straightforward Read category tool.
From the tool's definition Tool scans and returns a unique list of image URLs and their usage locations. Action verbs are 'scan' and 'returns' — purely retrieval with no modification, creation, deletion, or execution of operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs scan_unique_images safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_unique_images, this is the rule to start with:
scan_unique_images is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every scan_unique_images call is checked against it from then on.
Questions about scan_unique_images
Scan all images used across page sources, global sources, and global sections. Returns a unique list of image URLs with which elements use each one. Useful for: image audit, finding broken/duplicated CDN URLs, bulk replace planning, theme migration. Scans every string field in the source tree (config.src, style.background-image, etc.) and CSS url(...) refs — wide net catches all variants. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for scan_unique_images: 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 Webcake Storefront. Nothing to install.
scan_unique_images 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 scan_unique_images 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 scan_unique_images. 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.
scan_unique_images is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue