Low Risk

browser_take_screenshot

browser_take_screenshot

How to control browser_take_screenshot ↓

What browser_take_screenshot does on Amazon Redshift MCP Server

AI agents call browser_take_screenshot as a supporting operation in Amazon Redshift MCP Server workflows.

Low Risk

Why browser_take_screenshot needs a policy

The tool name suggests it takes a screenshot of a browser, which would be a read/capture operation with no destructive side effects. However, the description is completely empty, providing no confirmation of behavior. It seems out of place on an Amazon Redshift MCP server.

From the tool's definition Tool name is 'browser_take_screenshot'; description is empty and uninformative.

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

How to control browser_take_screenshot

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_take_screenshot": {
      "limits": [
        {
          "counter": "browser_take_screenshot_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_take_screenshot gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Redshift MCP Server — 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.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_take_screenshot

What does the browser_take_screenshot tool do? +

browser_take_screenshot. It is categorised as a Other tool in the Amazon Redshift MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on browser_take_screenshot? +

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

What risk level is browser_take_screenshot? +

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

Can I rate-limit browser_take_screenshot? +

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

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

browser_take_screenshot is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Redshift MCP Server tool call.

Start from Amazon Redshift MCP Server, 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.

805 Amazon Redshift MCP Server 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.