在 Gitee 仓库中创建或更新文件
AI agents use create_or_update_file to create or update resources in Gitee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitee environment.
This tool creates or modifies files in a Git repository, which are reversible write operations. While not destructive (files can be recovered via version history), it can modify repository content and potentially affect repository state, builds, or deployments.
From the tool's definition Tool name 'create_or_update_file' and description '在 Gitee 仓库中创建或更新文件' (create or update file in Gitee repository) explicitly indicates file creation and modification operations.
Documented attack patterns abuse exactly the kind of access create_or_update_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitee, and nothing reaches the server without passing your rules. This is the rule we recommend for create_or_update_file:
{
"version": "1",
"default": "deny",
"tools": {
"create_or_update_file": {
"limits": [
{
"counter": "create_or_update_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_or_update_file 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.
在 Gitee 仓库中创建或更新文件. It is categorised as a Write tool in the Gitee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitee MCP server in PolicyLayer and add a rule for create_or_update_file: 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 Gitee. Nothing to install.
create_or_update_file 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_or_update_file 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_or_update_file. 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_or_update_file is provided by the Gitee MCP server (normal-coder/gitee-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitee, 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.
20 Gitee tools catalogued and risk-classified — across an index of 43,000+ MCP servers.