Return the Redmine user tied to the API key.
AI agents call redmine_get_current_user to retrieve information from Redmine MCP server for Cursor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about the current authenticated user. It is a read-only operation that retrieves data without creating, modifying, deleting, or executing any operations. The blast radius is minimal—it only exposes user metadata tied to the API key, with no capability to alter system state.
From the tool's definition Tool name 'redmine_get_current_user' and description 'Return the Redmine user tied to the API key' indicate retrieval of user identity information with no modification or side effects.
Attacks that exploit this kind of access
Return the Redmine user tied to the API key. It is categorised as a Read tool in the Redmine MCP server for Cursor MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP server for Cursor MCP server in PolicyLayer and add a rule for redmine_get_current_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 for Cursor. Nothing to install.
redmine_get_current_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_current_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_current_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_current_user is provided by the Redmine MCP server for Cursor MCP server (mrajibh/redmine-mcp). 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 →