AI agents use save_rules_file to create or update resources in Trae Rules Generator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trae Rules Generator MCP environment.
This tool creates or modifies rule files in a filesystem. While the operation is reversible (files can be edited or deleted afterward), it directly alters the project's rule configuration. The blast radius is medium because misconfiguration could affect how Trae AI projects interpret rules, but the damage is not permanent or destructive.
From the tool's definition Tool name 'save_rules_file' and description '保存规则文件到指定目录' (save rules file to specified directory) indicate file creation/modification operations.
Documented attack patterns abuse exactly the kind of access save_rules_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trae Rules Generator MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for save_rules_file:
{
"version": "1",
"default": "deny",
"tools": {
"save_rules_file": {
"limits": [
{
"counter": "save_rules_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_rules_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.
保存规则文件到指定目录. It is categorised as a Write tool in the Trae Rules Generator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trae Rules Generator MCP server in PolicyLayer and add a rule for save_rules_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 Trae Rules Generator MCP. Nothing to install.
save_rules_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 save_rules_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 save_rules_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.
save_rules_file is provided by the Trae Rules Generator MCP server (xiaochenwin/trae-rules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Trae Rules Generator MCP, 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 Trae Rules Generator MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.