List all accessible Redmine projects. limit clamped to 1..100.
AI agents call list_projects 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 queries and returns project metadata without creating, modifying, or deleting any data. It is a straightforward read operation with minimal risk. Exposure is limited to disclosure of project names and metadata already filtered by OAuth authentication (accessible projects only). Severity is low due to no impact on system state or data integrity.
From the tool's definition Tool name 'list_projects' and description 'List all accessible Redmine projects' indicate a retrieval operation with no side effects. The limit parameter is a query control mechanism, not a destructive or modifying action.
Attacks that exploit this kind of access
List all accessible Redmine projects. limit clamped to 1..100. 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 list_projects: 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.
list_projects 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_projects 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_projects. 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_projects 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.
list_projects is one line of Redmine MCP OAuth Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →