get_screenshot

Get a specific screenshot by ID

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mickeydb-cobalt-strike-mcp/get-screenshot.md

WHAT IT DOES

What get_screenshot does on Cobalt Strike MCP Server

AI agents call get_screenshot to retrieve information from Cobalt Strike MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_screenshot is rated Low

This tool retrieves an existing screenshot without altering, executing, or destroying anything. It is a Read operation. However, the severity is high because screenshots from a compromised system contain sensitive information (screen contents, credentials visible on screen, confidential documents, etc.) that could be misused by an AI agent to exfiltrate data or inform further attacks.

From the tool's definition Tool name 'get_screenshot' and description 'Get a specific screenshot by ID' indicate a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_screenshot safely

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

get_screenshot Allowed

get_screenshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_screenshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every get_screenshot call is checked against it from then on.

FAQ

Questions about get_screenshot

What does the get_screenshot tool do? +

Get a specific screenshot by ID. It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_screenshot? +

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

What risk level is get_screenshot? +

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

Can I rate-limit get_screenshot? +

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

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

get_screenshot is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cobalt Strike MCP Server, and thousands of servers like it.

This server

All 220 Cobalt Strike MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →