AI agents call delete_time_entry to permanently remove resources in Redmine MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes time tracking records, which cannot be undone. Permanent deletion operations fall into the Destructive category, which is more severe than Write (which covers reversible modifications). The 'permanently' qualifier in the description confirms the irreversible nature.
From the tool's definition Tool name 'delete_time_entry' combined with description 'Delete a time record permanently' explicitly indicates irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete_time_entry gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redmine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_time_entry:
{
"version": "1",
"default": "deny",
"hide": [
"delete_time_entry"
]
}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.
Free to start. No card required.
Delete a time record permanently. It is categorised as a Destructive tool in the Redmine MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redmine MCP Server MCP server in PolicyLayer and add a rule for 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 Redmine MCP Server. Nothing to install.
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.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
delete_time_entry is provided by the Redmine MCP Server MCP server (yonaka15/mcp-server-redmine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Redmine MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Redmine MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.