execute_timestomp

What execute_timestomp does on Cobalt Strike MCP Server

AI agents invoke execute_timestomp 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 execute_timestomp is rated High

This tool performs active modification of system state (file timestamps) on a remote target, placing it in the Execute category rather than Write. The capability to alter timestamps is a post-exploitation technique commonly used to evade forensic detection. Given the red team/offensive context and potential for misuse to cover tracks of other malicious activities, severity is high.

From the tool's definition Tool modifies file timestamps, which requires executing code or system commands to alter file metadata. The Cobalt Strike context indicates this operates on a compromised target system where such timestamp modification could cover tracks of malicious activity.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_timestomp": {
      "limits": [
        {
          "counter": "execute_timestomp_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about execute_timestomp