AI agents call get_issue_relation 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 metadata about a relationship between issues in Redmine. The verb 'Get' and the query-like nature of fetching by ID are characteristic of Read operations. No data is created, modified, deleted, or executed. The blast radius of exposing this tool is minimal—it only returns existing relational information that may already be discoverable through other means.
From the tool's definition Tool name 'get_issue_relation' and description 'Get a single issue relation by ID' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Get a single issue relation by 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 get_issue_relation: 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_issue_relation 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_issue_relation 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_issue_relation. 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_issue_relation is provided by the Redmine MCP server (yenpu/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 →