Get the change history (journals) for a Redmine issue.
AI agents call get_issue_journals to retrieve information from Redmine MCP OAuth Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing change history data from a Redmine issue. It performs a read-only operation that does not create, modify, delete, execute code, or commit financial transactions. The action is non-destructive and has no side effects beyond data retrieval.
From the tool's definition Tool name 'get_issue_journals' and description 'Get the change history (journals) for a Redmine issue' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
Get the change history (journals) for a Redmine issue. It is categorised as a Read tool in the Redmine MCP OAuth Server MCP Server, which means it retrieves data without modifying state.
Register the Redmine MCP OAuth Server MCP server in PolicyLayer and add a rule for get_issue_journals: 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 OAuth Server. Nothing to install.
get_issue_journals 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_journals 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_journals. 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_journals is provided by the Redmine MCP OAuth Server MCP server (zh/redmine_mcp_py). 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 →