getCobaltStrikeWebsocketStatus
Get current status for Cobalt Strike WebSocket stream subscriptions.
This record as markdown: /tools/cobalt-strike-cobaltstrike-mcp-server/getcobaltstrikewebsocketstatus.md
What getCobaltStrikeWebsocketStatus does on Cobalt Strike MCP Server
AI agents call getCobaltStrikeWebsocketStatus 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.
Why getCobaltStrikeWebsocketStatus is rated Low
This tool retrieves status information about WebSocket subscriptions without creating, modifying, deleting, or executing any operations. It is purely informational in nature. While the server as a whole bridges to Cobalt Strike (a penetration testing framework), this specific tool performs only a read operation.
From the tool's definition Tool name 'getCobaltStrikeWebsocketStatus' and description 'Get current status for Cobalt Strike WebSocket stream subscriptions' indicate a status query operation with no modification or execution of commands.
Attacks that exploit this kind of access
The rule that runs getCobaltStrikeWebsocketStatus 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 getCobaltStrikeWebsocketStatus, this is the rule to start with:
getCobaltStrikeWebsocketStatus is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every getCobaltStrikeWebsocketStatus call is checked against it from then on.
Questions about getCobaltStrikeWebsocketStatus
Get current status for Cobalt Strike WebSocket stream subscriptions. It is categorised as a Read tool in the Cobalt Strike MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for getCobaltStrikeWebsocketStatus: 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.
getCobaltStrikeWebsocketStatus is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getCobaltStrikeWebsocketStatus 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.
Set action: deny in the PolicyLayer policy for getCobaltStrikeWebsocketStatus. 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.
getCobaltStrikeWebsocketStatus is provided by the Cobalt Strike MCP Server MCP server (cobalt-strike/cobaltstrike-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cobalt Strike MCP Server, and thousands of servers like it.
This server
Across the catalogue