Xem chi tiết issue kèm comments và lịch sử thay đổi.
AI agents call get_issue_detail to retrieve information from Redmine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs read-only access to Redmine issue data. It retrieves and displays existing information (issue details, comments, history) without creating, modifying, or deleting any data. The blast radius of misuse is minimal—an agent could access information but cannot harm the system or data integrity.
From the tool's definition Tool retrieves issue details including comments and change history. The description 'Xem chi tiết issue kèm comments và lịch sử thay đổi' translates to 'View issue details with comments and change history.' This is a query/retrieval operation with no…
Attacks that exploit this kind of access
Xem chi tiết issue kèm comments và lịch sử thay đổi. It is categorised as a Read tool in the Redmine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP Server MCP server in PolicyLayer and add a rule for get_issue_detail: 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. Nothing to install.
get_issue_detail 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_detail 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_detail. 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_detail is provided by the Redmine MCP Server MCP server (tuantrunglc/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 →