Ask the Yocoolab AI assistant to analyze a web page. Supports text questions with optional screenshot (vision) and page context. Useful for getting AI insights about a page layout, accessibility, or code structure.
AI agents invoke ai_analyze_page to trigger actions in Yocoolab. 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.
This tool invokes an external AI service to analyze a web page, which constitutes triggering an external operation. It is not a simple read/query of stored data; it sends a request to an AI backend that may fetch/render the page and run analysis. The most severe applicable category is Execute due to the external operation being triggered.
From the tool's definition "Ask the Yocoolab AI assistant to analyze a web page" and "optional screenshot (vision) and page context" — triggers an external AI operation/request against a live web page
Attacks that exploit this kind of access
Ask the Yocoolab AI assistant to analyze a web page. Supports text questions with optional screenshot (vision) and page context. Useful for getting AI insights about a page layout, accessibility, or code structure. It is categorised as a Execute tool in the Yocoolab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Yocoolab MCP server in PolicyLayer and add a rule for ai_analyze_page: 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 Yocoolab. Nothing to install.
ai_analyze_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ai_analyze_page 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 ai_analyze_page. 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.
ai_analyze_page is provided by the Yocoolab MCP server (yocoolab/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 →