get_killdate

A read tool on the Cobalt Strike MCP server.

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-killdate.md

WHAT IT DOES

What get_killdate does on Cobalt Strike MCP Server

AI agents call get_killdate 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_killdate is rated Low

This tool retrieves operational metadata (kill date configuration) from a Cobalt Strike beacon. While the underlying Cobalt Strike server is inherently dangerous (it's a commercial red team tool), this specific tool only reads information.

From the tool's definition Tool name 'get_killdate' and description 'Get kill date' indicate a query/retrieval operation. In the context of Cobalt Strike (red team operations), the kill date is a configuration parameter that specifies when a beacon should stop executing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_killdate Allowed

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

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

FAQ

Questions about get_killdate

What does the get_killdate tool do? +

get_killdate is a read tool on the Cobalt Strike MCP Server MCP server. 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_killdate? +

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

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

Can I rate-limit get_killdate? +

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

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

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