AI agents use archive_project 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.
Archiving a project modifies its state rather than deleting it. The action is reversible – projects can typically be unarchived – distinguishing it from Destructive actions. While it affects project visibility and access, it does not delete data or cause financial impact.
From the tool's definition 'Archive a project' – archives a project by changing its status/state, which is a reversible modification of data. Not irreversible deletion (which would be Destructive), but a state change that modifies project metadata.
Documented attack patterns abuse exactly the kind of access archive_project 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 archive_project:
{
"version": "1",
"default": "deny",
"tools": {
"archive_project": {
"limits": [
{
"counter": "archive_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive_project 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.
Archive a project. 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 archive_project: 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.
archive_project 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 archive_project 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 archive_project. 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.
archive_project 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.