Low Risk

cleanshot_capture_previous_area

Repeat the last taken screenshot

How to control cleanshot_capture_previous_area ↓

What cleanshot_capture_previous_area does on Cleanshot

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

Low Risk

Why cleanshot_capture_previous_area needs a policy

This tool captures/reads screen content by repeating the last screenshot area. It only reads visual data from the screen without modifying, deleting, or executing anything. The main risk is inadvertent capture of sensitive on-screen information, hence low severity.

From the tool's definition Repeat the last taken screenshot

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

How to control cleanshot_capture_previous_area

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

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

cleanshot_capture_previous_area 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 Cleanshot — 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.

Related tools and policies

Go deeper

Questions about cleanshot_capture_previous_area

What does the cleanshot_capture_previous_area tool do? +

Repeat the last taken screenshot. It is categorised as a Read tool in the Cleanshot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cleanshot_capture_previous_area? +

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

What risk level is cleanshot_capture_previous_area? +

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

Can I rate-limit cleanshot_capture_previous_area? +

Yes. Add a rate_limit block to the cleanshot_capture_previous_area 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 cleanshot_capture_previous_area completely? +

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

cleanshot_capture_previous_area is provided by the Cleanshot MCP server (jdorfman/cleanshot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cleanshot tool call.

Start from Cleanshot, 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.

19 Cleanshot tools catalogued and risk-classified — across an index of 43,000+ 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.