Get a Redmine user. Use 'current' for the authenticated user.
AI agents call get_user 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 user information from Redmine without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query. Severity is low because user information retrieval has minimal blast radius—the data retrieved is typically already accessible to authenticated users, and no destructive or financial operations are involved.
From the tool's definition Tool name is 'get_user' and description states 'Get a Redmine user', which is a retrieval operation with no side effects. The use of 'Get' verb and lack of any modification language confirms this is a query/fetch operation.
Attacks that exploit this kind of access
Get a Redmine user. Use 'current' for the authenticated user. 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 get_user: 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.
get_user 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 get_user 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 get_user. 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.
get_user 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 →