take_screenshot

Take a screenshot of the page

SERVERNcp SOURCE@portel/ncp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/take-screenshot.md

WHAT IT DOES

What take_screenshot does on Ncp

AI agents invoke take_screenshot to trigger actions in Ncp. 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.

RISK

Why take_screenshot is rated High

Taking a screenshot involves executing a browser/UI action to capture the current state of a page. While it only reads visual data, it requires executing an external operation (browser automation) to produce the output. It could expose sensitive on-screen information if misused, warranting a medium severity rating.

From the tool's definition 'Take a screenshot of the page' — triggers a browser action (capturing the current page state)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs take_screenshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For take_screenshot, this is the rule to start with:

take_screenshot Rate-limited

take_screenshot 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": {
    "take_screenshot": {
      "limits": [
        {
          "counter": "take_screenshot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every take_screenshot call is checked against it from then on.

FAQ

Questions about take_screenshot

What does the take_screenshot tool do? +

Take a screenshot of the page. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on take_screenshot? +

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

What risk level is take_screenshot? +

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

Can I rate-limit take_screenshot? +

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

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

take_screenshot is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →