AI agents call list_issue_journals 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.
Issue journals contain historical records and activity logs. Listing these records retrieves data without side effects. The context of the Redmine server (a project management system) and the presence of other clearly write/execute-oriented tools supports this as a retrieval operation. Confidence slightly reduced due to empty description, but tool name semantics are unambiguous.
From the tool's definition Tool name 'list_issue_journals' indicates retrieval of journal/activity records for an issue. The 'list' prefix and lack of modification verbs (create, update, delete, close) suggest read-only query behavior.
Documented attack patterns abuse exactly the kind of access list_issue_journals gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redmine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_issue_journals:
{
"version": "1",
"default": "deny",
"tools": {
"list_issue_journals": {}
}
}list_issue_journals is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_issue_journals. 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 list_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 Server. Nothing to install.
list_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 list_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 list_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.
list_issue_journals is provided by the Redmine MCP Server MCP server (snowild/redmine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Redmine MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Redmine MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.