capture · Shotbot MCP: Risk & Policy

WHAT IT DOES

What capture does on Shotbot Mcp

AI agents invoke capture to trigger actions in Shotbot Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why capture needs a policy

This tool initiates an external action (capturing a screenshot of a URL via an API), which constitutes executing an external operation. It is not purely a read since it submits a request that causes a remote service to perform work. The blast radius is medium since it could be used to probe internal/sensitive URLs or consume API credits, but it does not modify or delete data.

From the tool's definition 'Submit a screenshot capture request for a URL' — triggers an external operation (screenshot capture) against an arbitrary public URL

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

capture Rate-limited

capture stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "capture": {
      "limits": [
        {
          "counter": "capture_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Shotbot Mcp, so you can run agents against it safely.

FAQ

Questions about capture

What does the capture tool do? +

Submit a screenshot capture request for a URL. It is categorised as a Execute tool in the Shotbot Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on capture? +

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

What risk level is capture? +

capture is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit capture? +

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

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

capture is provided by the Shotbot MCP server (shotbot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.