screenshot_element

Screenshot a single DOM element by id from the last inspect_elements (tight crop).

Server Visual Annotation MCP mstocker1/visual_annotation_mcp
Category Read
Risk class Low
Parameters 00 required

What screenshot_element does on Visual Annotation MCP

AI agents call screenshot_element to retrieve information from Visual Annotation MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why screenshot_element needs a policy

This tool captures a visual snapshot of a DOM element—a read-only operation that queries and retrieves information from the page state. It has no capability to modify data, execute scripts, delete content, or trigger financial transactions. The tight crop screenshot is purely observational.

From the tool's definition screenshot_element performs a 'Screenshot a single DOM element by id...', which retrieves and displays visual data without modifying, deleting, or executing operations with external side effects.

Questions about screenshot_element

What does the screenshot_element tool do? +

Screenshot a single DOM element by id from the last inspect_elements (tight crop). It is categorised as a Read tool in the Visual Annotation MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on screenshot_element? +

Register the Visual Annotation MCP server in PolicyLayer and add a rule for screenshot_element: 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 Visual Annotation MCP. Nothing to install.

What risk level is screenshot_element? +

screenshot_element is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit screenshot_element? +

Yes. Add a rate_limit block to the screenshot_element 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.

How do I block screenshot_element completely? +

Set action: deny in the PolicyLayer policy for screenshot_element. 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.

What MCP server provides screenshot_element? +

screenshot_element is provided by the Visual Annotation MCP server (mstocker1/visual_annotation_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

screenshot_element is one line of Visual Annotation's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.