AI agents call list_issue_priorities 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 static configuration data (priority enumeration values) from Redmine. It has no side effects, cannot modify state, and presents no security risk beyond potential information disclosure of non-sensitive priority labels. The blast radius is minimal—misuse by an AI agent would only result in reading existing priority definitions.
From the tool's definition Tool name 'list_issue_priorities' and description 'List issue priority enumeration values' indicate data retrieval with no modification. The verb 'list' is a classic read-only operation that queries and returns existing enumeration data.
Attacks that exploit this kind of access
List issue priority enumeration values. 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 list_issue_priorities: 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.
list_issue_priorities 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 list_issue_priorities 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 list_issue_priorities. 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.
list_issue_priorities 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 →