keylog_dump

Get captured keystrokes. Auto-selects client.

SERVERClaude C2 SOURCE0xyg3n/claude-c2

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/0xyg3n-claude-c2/keylog-dump.md

WHAT IT DOES

What keylog_dump does on Claude C2

AI agents call keylog_dump to retrieve information from Claude C2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why keylog_dump is rated Low

While keylog_dump performs a read operation (retrieves data with no immediate modification or deletion), it accesses extremely sensitive information—captured keystrokes—which could include passwords, credentials, private messages, and authentication tokens.

From the tool's definition Tool name 'keylog_dump' and description 'Get captured keystrokes' indicate retrieval of previously captured keyboard input data. The 'Auto-selects client' qualifier shows it operates across multiple system contexts.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs keylog_dump safely

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

keylog_dump Allowed

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

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

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

FAQ

Questions about keylog_dump

What does the keylog_dump tool do? +

Get captured keystrokes. Auto-selects client. It is categorised as a Read tool in the Claude C2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on keylog_dump? +

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

What risk level is keylog_dump? +

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

Can I rate-limit keylog_dump? +

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

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

keylog_dump is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude C2, and thousands of servers like it.

This server

All 94 Claude C2 tools →

Across the catalogue

The MCP Attack Database →

Guides

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