Log spent time on an issue (POST /time_entries.json). Uses default activity id 164 if activity_id omitted.
AI agents use redmine_log_time to create or update resources in Redmine MCP server for Cursor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine MCP server for Cursor environment.
This tool creates a new time entry record in Redmine via a POST request. It writes data to the system but is reversible (time entries can be deleted). Misuse could result in falsified time records, but it has no destructive or financial consequences.
From the tool's definition Log spent time on an issue (POST /time_entries.json)
Attacks that exploit this kind of access
Log spent time on an issue (POST /time_entries.json). Uses default activity id 164 if activity_id omitted. It is categorised as a Write tool in the Redmine MCP server for Cursor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redmine MCP server for Cursor MCP server in PolicyLayer and add a rule for redmine_log_time: 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 for Cursor. Nothing to install.
redmine_log_time 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 redmine_log_time 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 redmine_log_time. 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.
redmine_log_time is provided by the Redmine MCP server for Cursor MCP server (mrajibh/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 →