This record as markdown: /tools/0xyg3n-claude-c2/timestomp.md
What timestomp does on Claude C2
AI agents call timestomp to permanently remove resources in Claude C2, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why timestomp is rated Critical
Modifying file timestamps is a well-known anti-forensics/evidence-tampering technique. Once timestamps are changed, the original values are lost (irreversible without prior backup), making this Destructive. The broader server context (amsi_bypass, bypassuac, browser_creds, defender_exclude) strongly indicates offensive/red-team or malicious use, raising severity to high.
From the tool's definition 'Modify file timestamps' — timestomping is a classic anti-forensic technique that irreversibly alters file metadata (creation, modification, access times) to obscure evidence of activity.
Attacks that exploit this kind of access
The rule that runs timestomp safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For timestomp, this is the rule to start with:
timestomp is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every timestomp call is checked against it from then on.
Questions about timestomp
Modify file timestamps. Auto-selects client. It is categorised as a Destructive tool in the Claude C2 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude C2 MCP server in PolicyLayer and add a rule for 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 Claude C2. Nothing to install.
timestomp is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
timestomp is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude C2, and thousands of servers like it.
Across the catalogue