Render raw HTML/CSS to an image. Perfect for generating OG images, social cards, email previews, and dynamic content from templates. No URL needed.
AI agents invoke render_html to trigger actions in PageShot 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.
Rendering arbitrary HTML/CSS is an Execute-class operation: it runs caller-supplied code in a browser/rendering engine. While the primary output is a static image, the rendering step can trigger JavaScript execution, external resource fetches, and other side effects depending on the HTML provided.
From the tool's definition 'Render raw HTML/CSS to an image' — executes arbitrary HTML/CSS content supplied by the caller, triggering a rendering engine to process and run that markup
Attacks that exploit this kind of access
Render raw HTML/CSS to an image. Perfect for generating OG images, social cards, email previews, and dynamic content from templates. No URL needed. It is categorised as a Execute tool in the PageShot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PageShot MCP server in PolicyLayer and add a rule for render_html: 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 PageShot MCP. Nothing to install.
render_html 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 render_html 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 render_html. 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.
render_html is provided by the PageShot MCP server (pageshot-mcp). 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 →