指定されたRedmineプロジェクトの特定のトラッカーで利用可能なIssueステータスの一覧を取得
AI agents call list_project_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 tool queries project status metadata without creating, modifying, deleting, or executing any operations. The narrow scope (listing statuses for configuration reference) and inability to alter data result in low severity. High confidence because the operation name and function are clearly informational.
From the tool's definition list_project_statuses retrieves a list of issue statuses available for a specific tracker in a designated Redmine project. The verb 'list' and the function of retrieving/querying data with no modification indicates a read-only operation.
Documented attack patterns abuse exactly the kind of access list_project_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 list_project_statuses:
{
"version": "1",
"default": "deny",
"tools": {
"list_project_statuses": {}
}
}list_project_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.
指定されたRedmineプロジェクトの特定のトラッカーで利用可能なIssueステータスの一覧を取得. 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_project_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.
list_project_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 list_project_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 list_project_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.
list_project_statuses is provided by the Redmine MCP Server MCP server (yonaka15/mcp-server-redmine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Redmine MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Redmine MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.