AI agents call list_issue_relations 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 queries and returns existing data about issue relations without creating, modifying, or deleting anything. It is a straightforward read operation that matches the Read category definition (retrieves or queries data; no side effects). The alpha status and limited scope pose minimal risk.
From the tool's definition Tool name contains 'list' and description states 'List all relations for a given Redmine issue. Returns each relation' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
[Alpha] List all relations for a given Redmine issue. Returns each relation. 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_relations: 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_relations 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_relations 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_relations. 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_relations 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 →