Open CleanShot
AI agents call cleanshot_self_timer as a supporting operation in Cleanshot workflows.
The description only says 'Open CleanShot', which suggests launching the application. Based on the name 'cleanshot_self_timer', it likely opens CleanShot with a self-timer capture mode, but this is inferred from context rather than the description. Opening an application is generally low-risk and doesn't clearly fit Read, Write, Execute, Destructive, or Financial categories.
From the tool's definition Tool description is simply 'Open CleanShot' — uninformative about what the tool actually does beyond opening the application.
Documented attack patterns abuse exactly the kind of access cleanshot_self_timer gives an agent:
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_self_timer:
{
"version": "1",
"default": "deny",
"tools": {
"cleanshot_self_timer": {
"limits": [
{
"counter": "cleanshot_self_timer_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}cleanshot_self_timer gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open CleanShot. It is categorised as a Other tool in the Cleanshot MCP Server, which means it performs auxiliary operations.
Register the Cleanshot MCP server in PolicyLayer and add a rule for cleanshot_self_timer: 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.
cleanshot_self_timer is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cleanshot_self_timer 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 cleanshot_self_timer. 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.
cleanshot_self_timer 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.
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.