Get details of a specific user
AI agents call get-user to retrieve information from Redmine MCP 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 a Redmine instance without modifying, creating, deleting, or executing any actions. It is a straightforward query operation that poses minimal security risk if misused by an AI agent, as it only exposes existing user data. The severity is low because unauthorized read access to user details, while a privacy concern, does not cause data loss or system compromise.
From the tool's definition Tool name 'get-user' and description 'Get details of a specific user' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of fetching user details align with the Read category.
Attacks that exploit this kind of access
Get details of a specific user. It is categorised as a Read tool in the Redmine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP 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 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 Server MCP server (tamu960925/mcp-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 →