Generic Redmine API tool. Use this for any supported endpoint and operation.
AI agents invoke redmine_api_request to trigger actions in Redmine MCP server for Cursor. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This is a generic API execution tool that can perform any operation against the Redmine REST API, including reads, writes, updates, and deletions. Because it covers all supported endpoints and operations, it could be used to delete issues, projects, users, or other data irreversibly.
From the tool's definition "Generic Redmine API tool. Use this for any supported endpoint and operation."
Attacks that exploit this kind of access
Generic Redmine API tool. Use this for any supported endpoint and operation. It is categorised as a Execute tool in the Redmine MCP server for Cursor MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Redmine MCP server for Cursor MCP server in PolicyLayer and add a rule for redmine_api_request: 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 for Cursor. Nothing to install.
redmine_api_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the redmine_api_request 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 redmine_api_request. 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.
redmine_api_request is provided by the Redmine MCP server for Cursor MCP server (mrajibh/redmine-mcp). 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 →