AI agents use folder_rename to create or update resources in MCP Server for Unity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server for Unity environment.
Renaming a folder modifies project metadata and structure reversibly. It is not destructive (the folder and contents remain) and does not delete or irreversibly alter data. It is a Write operation as it changes the state of the project. Severity is medium because incorrect renaming could break build references or script imports, requiring manual correction, but the action is reversible by renaming back.
From the tool's definition Tool name 'folder_rename' and description 'Rename a folder in Unity project' indicate modification of project structure.
Documented attack patterns abuse exactly the kind of access folder_rename gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Unity, and nothing reaches the server without passing your rules. This is the rule we recommend for folder_rename:
{
"version": "1",
"default": "deny",
"tools": {
"folder_rename": {
"limits": [
{
"counter": "folder_rename_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}folder_rename 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.
Rename a folder in Unity project. It is categorised as a Write tool in the MCP Server for Unity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server for Unity MCP server in PolicyLayer and add a rule for folder_rename: 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 Server for Unity. Nothing to install.
folder_rename 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 folder_rename 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 folder_rename. 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.
folder_rename is provided by the MCP Server for Unity MCP server (zabaglione/mcp-server-unity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Unity, 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.
15 MCP Server for Unity tools catalogued and risk-classified — across an index of 43,000+ MCP servers.