execute_timestomp · Cobalt Strike MCP Server MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why execute_timestomp needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_timestomp Rate-limited

execute_timestomp 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": {
    "execute_timestomp": {
      "limits": [
        {
          "counter": "execute_timestomp_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 execute_timestomp

What does the execute_timestomp tool do? +

Modify file timestamps. 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 execute_timestomp? +

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

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

Can I rate-limit execute_timestomp? +

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

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

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