AI agents use create_new_issue to create or update resources in Redmine MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine MCP Server environment.
Creating a new issue is a reversible Write operation that adds data to the system. While the tool description is empty (slightly lowering confidence), the tool name and context from sibling tools clearly indicate it modifies Redmine data.
From the tool's definition Tool name 'create_new_issue' combined with sibling tools like 'add_issue_note', 'assign_issue', 'close_issue' establishes this server's focus on issue management and data modification. The verb 'create' indicates the tool creates a new record in Redmine.
Documented attack patterns abuse exactly the kind of access create_new_issue 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 create_new_issue:
{
"version": "1",
"default": "deny",
"tools": {
"create_new_issue": {
"limits": [
{
"counter": "create_new_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_new_issue stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_new_issue. It is categorised as a Write tool in the Redmine MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redmine MCP Server MCP server in PolicyLayer and add a rule for create_new_issue: 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.
create_new_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_new_issue 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 create_new_issue. 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.
create_new_issue 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.