List Redmine users (requires admin). limit clamped to 1..100.
AI agents call list_users 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 performs a read-only query of user data. While it requires admin privileges and could expose user information, it does not modify, delete, execute code, or commit financial actions. The clamped limit parameter reduces potential for abuse. Classification as Read with low severity is appropriate given the informational nature and administrative safeguards.
From the tool's definition Tool description states 'List Redmine users' - a retrieval operation with no data modification. The limit parameter (1..100) constrains query scope and prevents unbounded data extraction.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List Redmine users (requires admin). 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_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 MCP OAuth Server. Nothing to install.
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 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 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.
list_users 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.
list_users is one line of Redmine MCP OAuth Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →