List issues from Redmine with optional filtering
AI agents call list-issues 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.
This tool queries and retrieves issue data from Redmine with optional filters applied, but performs no modifications, deletions, or external operations. It has no side effects on the system state. The blast radius if misused by an AI agent is minimal—at worst, filtered issue data is returned to the agent, which does not affect system integrity or cause harm.
From the tool's definition Tool name 'list-issues' and description 'List issues from Redmine with optional filtering' indicate data retrieval without modification. The verb 'list' is explicitly enumerated as a Read operation.
Attacks that exploit this kind of access
List issues from Redmine with optional filtering. 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-issues: 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-issues 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-issues 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-issues. 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-issues is provided by the Redmine MCP Server MCP server (tamu960925/mcp-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 →