inject_keylogger · Cobalt Strike MCP Server MCP

WHAT IT DOES

What inject_keylogger does on Cobalt Strike MCP Server

AI agents invoke inject_keylogger to trigger actions in Cobalt Strike MCP Server. 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.

WHY IT NEEDS A POLICY

Why inject_keylogger needs a policy

This tool executes a keylogger injection into a running process, which is a code execution action with severe security implications. It captures sensitive user input (credentials, messages, commands) and represents a critical capability for unauthorized system monitoring.

From the tool's definition Tool is named 'inject_keylogger' and described as 'Start keylogger on a process' - this executes code injection and starts monitoring operations on a target process without reversibility of the monitoring state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

inject_keylogger Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cobalt Strike MCP Server, so you can run agents against it safely.

FAQ

Questions about inject_keylogger

What does the inject_keylogger tool do? +

Start keylogger on a process. It is categorised as a Execute tool in the Cobalt Strike MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on inject_keylogger? +

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

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

Can I rate-limit inject_keylogger? +

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

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

inject_keylogger 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.