Critical Risk →

delete_estimate

Delete an estimate.

How to control delete_estimate ↓

AI agents call delete_estimate to permanently remove resources in Harvest MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deletion of estimates cannot be undone and represents irreversible data loss. This is a destructive operation that could impact business records, financial tracking, and client relationships. While not directly financial, the estimate itself may represent committed pricing or billing information, making accidental deletion a serious concern.

From the tool's definition Tool name is 'delete_estimate' with description 'Delete an estimate.' The verb 'delete' directly indicates irreversible removal of data.

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

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 delete_estimate:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_estimate"
  ]
}

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

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

Free to start. No card required.

Go deeper

What does the delete_estimate tool do? +

Delete an estimate. 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 delete_estimate? +

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

delete_estimate 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 delete_estimate? +

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

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

delete_estimate is provided by the Harvest MCP Server MCP server (taiste/harvest-mcp-server). 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.

Deterministic rules across all 21 Harvest MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 Harvest MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.