AI agents call redmine_list_users to retrieve information from Redmine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user data (IDs, logins, emails) without modifying or deleting anything. It is a Read operation. Severity is medium because exposing user lists (especially email addresses and login names) could enable social engineering, credential attacks, or targeted exploitation, though it does not directly compromise systems or data integrity.
From the tool's definition Tool name 'redmine_list_users' and description 'List Redmine users... Returns user IDs, login names, and email addresses' indicate a retrieval operation with no side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
[Stable] List Redmine users. Requires admin privileges. Returns user IDs, login names, and email addresses. It is categorised as a Read tool in the Redmine MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP server in PolicyLayer and add a rule for redmine_list_users: 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.
redmine_list_users 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 redmine_list_users 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_list_users. 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_list_users is provided by the Redmine MCP server (jesusr00/mcp-server-redmine). 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 →