Low Risk

take_screenshot

[LEGACY] Take a screenshot of the current page. Use interact_with_page instead.

How to control take_screenshot ↓

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

Low Risk

Taking a screenshot is a read-only operation that captures the current visual state of a page. No data is created, modified, or deleted. The [LEGACY] tag and redirect to interact_with_page slightly lower confidence, but the described action is purely observational.

From the tool's definition 'Take a screenshot of the current page' - captures visual state without modifying anything

Documented attack patterns abuse exactly the kind of access take_screenshot gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for take_screenshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "take_screenshot": {}
  }
}

take_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ZMCPTools — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the take_screenshot tool do? +

[LEGACY] Take a screenshot of the current page. Use interact_with_page instead. It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on take_screenshot? +

Register the ZMCPTools MCP server in PolicyLayer and add a rule for take_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 ZMCPTools. Nothing to install.

What risk level is take_screenshot? +

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

Can I rate-limit take_screenshot? +

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

How do I block take_screenshot completely? +

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

What MCP server provides take_screenshot? +

take_screenshot is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ZMCPTools tool call.

Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.