delete_timecamp_time_entry
AI agents call delete_timecamp_time_entry to permanently remove resources in TimeCamp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting time entries is an irreversible action that cannot be undone without manual intervention. This is a classic destructive operation that destroys recorded data. While the blast radius is narrower than a wholesale database drop, accidental deletion of time entries (especially multiple or critical ones) would require manual recovery or data restoration.
From the tool's definition Tool name is 'delete_timecamp_time_entry' — the verb 'delete' combined with direct object 'time_entry' indicates irreversible removal of data records.
Attacks that exploit this kind of access
delete_timecamp_time_entry. It is categorised as a Destructive tool in the TimeCamp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TimeCamp MCP Server MCP server in PolicyLayer and add a rule for delete_timecamp_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 TimeCamp MCP Server. Nothing to install.
delete_timecamp_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_timecamp_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_timecamp_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_timecamp_time_entry is provided by the TimeCamp MCP Server MCP server (timecamp-org/timecamp-mcp-server). 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 →