Delete a time entry for a change.
AI agents call delete_change_time_entry to permanently remove resources in Freshservice MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of a time entry record. While the blast radius is somewhat limited to a single time entry artifact (not cascading deletes of entire changes), deletion cannot be undone and represents loss of tracked work data. This is more severe than Write (which is reversible) and meets the Destructive category definition.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a time entry for a change' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a time entry for a change. It is categorised as a Destructive tool in the Freshservice MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for delete_change_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 Freshservice MCP Server. Nothing to install.
delete_change_time_entry 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 delete_change_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.
Set action: deny in the PolicyLayer policy for delete_change_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.
delete_change_time_entry is provided by the Freshservice MCP Server MCP server (leemangold/freshservice_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →