AI agents call get_issue_statuses 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 is a straightforward data retrieval operation that queries the Redmine system for reference data (available statuses). It has no side effects, does not modify any data, and poses minimal security risk. Misuse by an AI agent would only result in information disclosure of non-sensitive configuration data, not operational harm.
From the tool's definition Tool retrieves 'a list of all available issue statuses' with no modification or deletion of data; purely a query operation.
Documented attack patterns abuse exactly the kind of access get_issue_statuses 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 get_issue_statuses:
{
"version": "1",
"default": "deny",
"tools": {
"get_issue_statuses": {}
}
}get_issue_statuses 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.
Get a list of all available issue statuses. 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_statuses: 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_statuses 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_statuses 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_statuses. 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_statuses 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.