AI agents call get_role 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.
This tool retrieves role metadata and permission information without modifying any state. It is a straightforward data lookup operation characteristic of Read-category tools. The low severity reflects minimal blast radius—unauthorized role information disclosure is generally low risk compared to modification or deletion of data.
From the tool's definition Tool name and description explicitly state 'Get a role by id', which is a read-only query operation. The description indicates it retrieves and displays role information and permissions, with no modification or side effects implied.
Attacks that exploit this kind of access
Get a role by id, including its permissions list. 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 get_role: 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.
get_role 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_role 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_role. 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_role is provided by the Redmine MCP server (KalvadTech/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 →