Rename an existing folder in PromptingBox.
AI agents use rename_folder to create or update resources in PromptingBox MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PromptingBox MCP Server environment.
Renaming a folder is a reversible write operation. It modifies metadata but does not execute code, delete data, move money, or cause irreversible changes. The impact is limited to folder organization within PromptingBox. Severity is low because misuse would only clutter the user's folder structure, which can be easily corrected.
From the tool's definition Tool description states "Rename an existing folder" — a modification operation that changes folder metadata. The name and description indicate this reversibly updates data (folder name) without deletion or execution of code.
Attacks that exploit this kind of access
Rename an existing folder in PromptingBox. It is categorised as a Write tool in the PromptingBox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PromptingBox MCP Server MCP server in PolicyLayer and add a rule for rename_folder: 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 PromptingBox MCP Server. Nothing to install.
rename_folder 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 rename_folder 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 rename_folder. 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.
rename_folder is provided by the PromptingBox MCP Server MCP server (promptingbox/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →