AI agents use create_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.
Creating a time entry is a write operation that adds new data to the Redmine system. While time tracking is generally low-risk, it can affect project management, billing, and team metrics. The severity is medium because misuse could distort project timelines and financial reporting, but the data is not irreversibly destroyed and can be corrected.
From the tool's definition Tool description states 'Log time spent on an issue or project.' The verb 'log' indicates creation of a time entry record, which is a write operation that modifies project data (adds a new time entry).
Attacks that exploit this kind of access
Log time spent on an issue or project. 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.
Register the Redmine 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. Nothing to install.
create_time_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_time_entry is provided by the Redmine MCP server (yenpu/redmine-mcp). 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 →