Find known image assets within a screenshot. Uses template matching
AI agents call find_assets_in_screenshot to retrieve information from Layout Detector MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and identifies visual information from existing screenshots without modifying, executing code, deleting data, or moving money. It is a pure analysis/query function that scans imagery and returns positional data about detected assets. The minimal blast radius of misuse (returning incorrect coordinates or false positives) does not escalate beyond low severity.
From the tool's definition Tool 'find_assets_in_screenshot' performs template matching to locate image assets within a screenshot—a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access find_assets_in_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Layout Detector MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for find_assets_in_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"find_assets_in_screenshot": {}
}
}find_assets_in_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find known image assets within a screenshot. Uses template matching. It is categorised as a Read tool in the Layout Detector MCP MCP Server, which means it retrieves data without modifying state.
Register the Layout Detector MCP server in PolicyLayer and add a rule for find_assets_in_screenshot: 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 Layout Detector MCP. Nothing to install.
find_assets_in_screenshot 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 find_assets_in_screenshot 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 find_assets_in_screenshot. 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.
find_assets_in_screenshot is provided by the Layout Detector MCP server (katlis/layout-detector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Layout Detector MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Layout Detector MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.