redmine_update_time_entry · Redmine MCP: Risk & Policy

WHAT IT DOES

What redmine_update_time_entry does on Redmine

AI agents use redmine_update_time_entry to create or update resources in Redmine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine environment.

WHY IT NEEDS A POLICY

Why redmine_update_time_entry needs a policy

The tool modifies an existing time entry record but does not delete or destroy data. Time entry updates are reversible through subsequent corrections. While this could affect organizational records and reporting, the impact is limited to data modification without financial transaction execution, making it Write rather than Execute or Financial.

From the tool's definition Tool name contains 'update' and description states 'Update an existing Redmine time entry. Only provided fields are changed.' This is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

redmine_update_time_entry Rate-limited

redmine_update_time_entry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "redmine_update_time_entry": {
      "limits": [
        {
          "counter": "redmine_update_time_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Redmine, so you can run agents against it safely.

FAQ

Questions about redmine_update_time_entry

What does the redmine_update_time_entry tool do? +

[Stable] Update an existing Redmine time entry. Only provided fields are changed. It is categorised as a Write tool in the Redmine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on redmine_update_time_entry? +

Register the Redmine MCP server in PolicyLayer and add a rule for redmine_update_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. Nothing to install.

What risk level is redmine_update_time_entry? +

redmine_update_time_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit redmine_update_time_entry? +

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

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

redmine_update_time_entry is provided by the Redmine MCP server (jesusr00/mcp-server-redmine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.