get_keystrokes

Get keystroke data 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-keystrokes.md

WHAT IT DOES

What get_keystrokes does on Cobalt Strike MCP Server

AI agents call get_keystrokes 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_keystrokes is rated Low

This tool retrieves keystroke data, making it a Read category tool. However, the severity is high because keystroke logs contain highly sensitive information (passwords, PII, credentials, private communications) that could enable further attacks or data exfiltration if obtained by an unauthorized agent.

From the tool's definition Tool name 'get_keystrokes' and description 'Get keystroke data by ID' indicate retrieval of previously captured keystroke logs. This is a read operation that retrieves sensitive data (keystrokes) without modifying or deleting it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_keystrokes 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_keystrokes, this is the rule to start with:

get_keystrokes Allowed

get_keystrokes 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_keystrokes": {}
  }
}

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_keystrokes call is checked against it from then on.

FAQ

Questions about get_keystrokes

What does the get_keystrokes tool do? +

Get keystroke data 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_keystrokes? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for get_keystrokes: 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_keystrokes? +

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

Can I rate-limit get_keystrokes? +

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

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

get_keystrokes 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 →