AI agents use upload_files to create or update resources in Gitea MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitea MCP Server environment.
This tool creates or modifies files in a repository, which is reversible via deletion or overwrite. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial).
From the tool's definition Tool name 'upload_files' and description 'Upload files to Gitea repository' directly indicate file creation/modification operations.
Documented attack patterns abuse exactly the kind of access upload_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitea MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_files:
{
"version": "1",
"default": "deny",
"tools": {
"upload_files": {
"limits": [
{
"counter": "upload_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_files 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 files to Gitea repository. It is categorised as a Write tool in the Gitea MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitea MCP Server MCP server in PolicyLayer and add a rule for upload_files: 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 Gitea MCP Server. Nothing to install.
upload_files 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 upload_files 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 upload_files. 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.
upload_files is provided by the Gitea MCP Server MCP server (mushroomfleet/gitea-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitea 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.
4 Gitea MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.