AI agents call redmine_get_user 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.
The tool retrieves user information by ID with no side effects. This is a straightforward read operation that merely fetches and returns existing data. No data is created, modified, deleted, or financial transactions are involved. Low severity because user metadata retrieval poses minimal risk even if called inappropriately by an agent.
From the tool's definition 'Get details of a single Redmine user by numeric ID' - this is a retrieval operation that queries user information without modifying or deleting any data.
Attacks that exploit this kind of access
[Stable] Get details of a single Redmine user by numeric ID. 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_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. Nothing to install.
redmine_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 redmine_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 redmine_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.
redmine_get_user 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 →