List Redmine time entries with optional filters. limit clamped to 1..100.
AI agents call list_time_entries to retrieve information from Redmine MCP OAuth Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries time entry data from Redmine with no side effects. It is a straightforward Read operation that poses minimal risk even if an AI agent misuses it, as it cannot modify, delete, or execute actions—it can only fetch existing data subject to access controls.
From the tool's definition Tool name 'list_time_entries' and description 'List Redmine time entries' indicate a retrieval operation. The phrase 'with optional filters' and 'limit clamped' confirm query functionality without modification.
Attacks that exploit this kind of access
List Redmine time entries with optional filters. limit clamped to 1..100. It is categorised as a Read tool in the Redmine MCP OAuth Server MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP OAuth Server MCP server in PolicyLayer and add a rule for list_time_entries: 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.
list_time_entries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_time_entries 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 list_time_entries. 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.
list_time_entries 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.
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 →