// SCAN REPORT

Shotbot Mcp

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 6 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 06/07/2026

How to control Shotbot Mcp ↓

TOOL MAP

What Shotbot Mcp exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Shotbot Mcp tools

Execute · Medium capture This tool initiates an external action (capturing a screenshot of a URL via an API), which constitutes executing an external operation.

1 of Shotbot Mcp's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Shotbot Mcp

PolicyLayer is an MCP gateway — it sits between your AI agents and Shotbot Mcp, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "account_status": {
    "limits": [
      {
        "counter": "account_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Shotbot Mcp — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SHOTBOT →

Instant setup, no code required.

FULL CATALOGUE

All 3 Shotbot Mcp tools

EXECUTE 1 tools

Execute capture Submit a screenshot capture request for a URL.

READ 2 tools

Read account_status Get the current account status: plan (free | pro), credit balance, monthly quota usage, Read get_status Poll the status of a capture by token.

FAQ

Questions about Shotbot Mcp

Is the Shotbot MCP server safe to use without restrictions? +

The Shotbot Mcp server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Shotbot MCP server expose? +

3 tools across 1 categories: Read. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Shotbot Mcp? +

Register the Shotbot MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Shotbot Mcp tool call.

Deterministic rules across all 3 Shotbot Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SHOTBOT →

Instant setup, no code required.

3 Shotbot Mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.