cleanshot_pin

THE RISK

Low Risk

Why cleanshot_pin needs a policy

This tool opens/displays a file as a pinned screenshot overlay. It reads and displays content without modifying, deleting, or executing anything. The primary action is viewing/displaying, which is a read operation.

From the tool's definition Open a file as a pinned screenshot

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

POLICY

How to control cleanshot_pin

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_pin:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cleanshot_pin": {}
  }
}

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

Create a free account and register Cleanshot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Cleanshot tools

Execute cleanshot_all_in_one Launch CleanShot Execute cleanshot_capture_area Open CleanShot Execute cleanshot_capture_text Open CleanShot Execute cleanshot_hide_desktop_icons Hide desktop icons Execute cleanshot_open_annotate Open a file in CleanShot Execute cleanshot_open_history Open CleanShot Execute cleanshot_open_settings Open CleanShot settings with optional tab Execute cleanshot_record_screen Open CleanShot

All 19 Cleanshot tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cleanshot_pin

What does the cleanshot_pin tool do? +

Open a file as a pinned 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_pin? +

Register the Cleanshot MCP server in PolicyLayer and add a rule for cleanshot_pin: 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_pin? +

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

Can I rate-limit cleanshot_pin? +

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

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

cleanshot_pin 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.

CHECK YOUR STACK →