Capture high-quality screenshots of web pages in base64 encoded JPEG format. Use this tool when you need to visually inspect a website, take a snapshot for analysis, or show users what a webpage looks like.
AI agents call capture_screenshot_url to retrieve information from Jina AI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | The complete HTTP/HTTPS URL of the webpage to capture (e.g., 'https://example.com') |
return_url | boolean | — | Set to true to return screenshot URLs instead of downloading images as base64 |
firstScreenOnly | boolean | — | Set to true for a single screen capture (faster), false for full page capture including content below the fold |
Parameters from the server's own tool schema.
The tool fetches and renders a web page as an image (base64 JPEG), which is purely a read/retrieval operation. It does not modify, write, or delete any data, nor does it execute code or trigger financial operations. The only potential concern is visiting arbitrary URLs, but that is inherent to any web-fetch operation and carries low blast radius.
From the tool's definition 'Capture high-quality screenshots of web pages' and 'visually inspect a website, take a snapshot for analysis' — retrieves a visual representation of a page with no side effects
Risk signalsAccepts URL/endpoint input (url)
Documented attack patterns abuse exactly the kind of access capture_screenshot_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jina AI, and nothing reaches the server without passing your rules. This is the rule we recommend for capture_screenshot_url:
{
"version": "1",
"default": "deny",
"tools": {
"capture_screenshot_url": {}
}
}capture_screenshot_url 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.
Capture high-quality screenshots of web pages in base64 encoded JPEG format. Use this tool when you need to visually inspect a website, take a snapshot for analysis, or show users what a webpage looks like. It is categorised as a Read tool in the Jina AI MCP Server, which means it retrieves data without modifying state.
capture_screenshot_url accepts 3 parameters: url, return_url, firstScreenOnly. The full parameter table on this page comes from the server's own tool schema.
Register the Jina AI MCP server in PolicyLayer and add a rule for capture_screenshot_url: 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 Jina AI. Nothing to install.
capture_screenshot_url 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 capture_screenshot_url 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 capture_screenshot_url. 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.
capture_screenshot_url is provided by the Jina AI MCP server (jina). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jina AI, 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.
21 Jina AI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.