create_time_entry · Redmine MCP OAuth Server MCP

WHAT IT DOES

What create_time_entry does on Redmine MCP OAuth Server

AI agents use create_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 create_time_entry needs a policy

Creating a time entry is a write operation that adds structured data to Redmine's time tracking system. While it could have downstream effects on reporting and billing (hence medium rather than low severity), time entries are typically editable and deletable, making them reversible modifications. This distinguishes it from Destructive operations.

From the tool's definition The tool 'create_time_entry' performs a logging operation that 'creates' time entry records in Redmine, which are reversible modifications to the time tracking system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_time_entry Rate-limited

create_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": {
    "create_time_entry": {
      "limits": [
        {
          "counter": "create_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 create_time_entry

What does the create_time_entry tool do? +

Log time on a Redmine issue or project. 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 create_time_entry? +

Register the Redmine MCP OAuth Server MCP server in PolicyLayer and add a rule for create_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 create_time_entry? +

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

Can I rate-limit create_time_entry? +

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

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

create_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.