Upload a file to Redmine and get a token for attachment Args: file_path: Fully qualified path to the file to upload (must be within REDMINE_ALLOWED_DIRECTORIES) description: Optional description for the file Returns: str: YAML string containing response status code, body and error message The bod...
AI agents use redmine_upload to create or update resources in MCP Redmine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Redmine environment.
This tool creates new file attachments in Redmine, which is a reversible write operation. While uploads can be problematic if an AI agent uploads malicious content or sensitive files without authorization, the operation itself is not destructive (files can be removed) and doesn't execute code or move money.
From the tool's definition Tool description states 'Upload a file to Redmine and get a token for attachment' — this is a create/write operation that persists data to the Redmine system. The args include file_path and optional description, indicating file creation.
Documented attack patterns abuse exactly the kind of access redmine_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Redmine, and nothing reaches the server without passing your rules. This is the rule we recommend for redmine_upload:
{
"version": "1",
"default": "deny",
"tools": {
"redmine_upload": {
"limits": [
{
"counter": "redmine_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}redmine_upload 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.
Upload a file to Redmine and get a token for attachment Args: file_path: Fully qualified path to the file to upload (must be within REDMINE_ALLOWED_DIRECTORIES) description: Optional description for the file Returns: str: YAML string containing response status code, body and error message The body contains the attachment token. It is categorised as a Write tool in the MCP Redmine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Redmine MCP server in PolicyLayer and add a rule for redmine_upload: 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 MCP Redmine. Nothing to install.
redmine_upload 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 redmine_upload 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_upload. 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_upload is provided by the MCP Redmine MCP server (runekaagaard/mcp-redmine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 MCP Redmine tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 MCP Redmine tools catalogued and risk-classified — across an index of 42,500+ MCP servers.