update_time_entry · Redmine MCP OAuth Server MCP

WHAT IT DOES

What update_time_entry does on Redmine MCP OAuth Server

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

WHY IT NEEDS A POLICY

Why update_time_entry needs a policy

This tool modifies existing time entry records in Redmine by changing specified fields. This is a Write operation—it creates or updates data reversibly. While time entries often relate to billing and project management, the tool itself does not directly move money or create financial obligations (Financial category); it only modifies the data that might inform financial calculations.

From the tool's definition The tool name 'update_time_entry' and description 'Update a Redmine time entry. `updates` is a dict of fields to change' indicate a modification operation on existing data in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_time_entry Rate-limited

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": {
    "update_time_entry": {
      "limits": [
        {
          "counter": "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 MCP OAuth Server, so you can run agents against it safely.

FAQ

Questions about update_time_entry

What does the update_time_entry tool do? +

Update a Redmine time entry. updates is a dict of fields to change. It is categorised as a Write tool in the Redmine MCP OAuth Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_time_entry? +

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

What risk level is update_time_entry? +

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

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

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

update_time_entry is provided by the Redmine MCP OAuth Server MCP server (zh/redmine_mcp_py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.