inject_screenwatch · Cobalt Strike MCP Server MCP

WHAT IT DOES

What inject_screenwatch does on Cobalt Strike MCP Server

AI agents invoke inject_screenwatch 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_screenwatch needs a policy

Screen watching via injection is an Execute action—it triggers an external operation (screen capture and monitoring) whose effects depend on the target process and system state. While it doesn't directly modify data, it performs active monitoring/surveillance through code injection.

From the tool's definition 'Start screen watch (inject mode)' enables execution of screen capture functionality via injection, which constitutes code/operation execution with external side effects. The inject mode indicates direct process manipulation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

inject_screenwatch Rate-limited

inject_screenwatch 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_screenwatch": {
      "limits": [
        {
          "counter": "inject_screenwatch_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_screenwatch

What does the inject_screenwatch tool do? +

Start screen watch (inject mode). 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_screenwatch? +

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

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

Can I rate-limit inject_screenwatch? +

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

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

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