harvest_delete_time_entry

THE RISK

Critical Risk

Why harvest_delete_time_entry needs a policy

This tool permanently removes time entry records from Harvest, which cannot be undone. Deleted time entries cannot be recovered through the tool's normal API surface. Since time entries are financial records (hours logged for billing/payroll), their irreversible deletion could impact financial accuracy, invoicing, and payroll calculations. This places it in the Destructive category.

From the tool's definition Tool name is 'harvest_delete_time_entry' and description states 'Delete a time entry. Use this to remove erroneous or unwanted time entries.' The verb 'delete' and explicit removal action indicate irreversible destruction of data.

Documented attack patterns abuse exactly the kind of access harvest_delete_time_entry gives an agent:

POLICY

How to control harvest_delete_time_entry

PolicyLayer is an MCP gateway — it sits between your AI agents and Harvest MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for harvest_delete_time_entry:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "harvest_delete_time_entry"
  ]
}

harvest_delete_time_entry disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Harvest MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Harvest MCP Server tools

Write harvest_stop_timer Stop a running timer on a time entry Write harvest_create_time_entry Create a new time entry Read harvest_compute_budget_performance Analyze employee performance based on budget adherence per project. Compares actual hours Read harvest_aggregate_time Aggregate time entries by various dimensions. Simple convenience tool for getting total ho Read harvest_compute_profitability Compute profitability metrics for a date range. Supports three modes: time_based (hours r Read harvest_compute_utilization Compute utilization metrics for a date range. Shows how much of available capacity is bein Read harvest_get_company Get information about the authenticated Harvest company/account Read harvest_get_current_user Get information about the currently authenticated Harvest user

All 21 Harvest MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Harvest MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about harvest_delete_time_entry

What does the harvest_delete_time_entry tool do? +

Delete a time entry. Use this to remove erroneous or unwanted time entries. It is categorised as a Destructive tool in the Harvest MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on harvest_delete_time_entry? +

Register the Harvest MCP Server MCP server in PolicyLayer and add a rule for harvest_delete_time_entry: 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 Harvest MCP Server. Nothing to install.

What risk level is harvest_delete_time_entry? +

harvest_delete_time_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit harvest_delete_time_entry? +

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

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

harvest_delete_time_entry is provided by the Harvest MCP Server MCP server (southleft/harvest-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Harvest MCP Server tool call.

Start from Harvest MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →