Renames or moves a file/directory
AI agents use fs_rename to create or update resources in Mcp Ssh Tool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ssh Tool environment.
Renaming and moving files are Write operations because they modify data organization reversibly. Severity is high because autonomous SSH execution on remote systems could rename critical files (application configs, system files) causing service failures or data inaccessibility. The context of autonomous SSH operations without manual prompts increases blast radius if an agent makes incorrect rename decisions.
From the tool's definition Tool description states 'Renames or moves a file/directory'. These operations modify filesystem state reversibly (can be undone by renaming back or moving to original location), but do not delete data.
Attacks that exploit this kind of access
Renames or moves a file/directory. It is categorised as a Write tool in the Mcp Ssh Tool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ssh Tool MCP server in PolicyLayer and add a rule for fs_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 Ssh Tool. Nothing to install.
fs_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 fs_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 fs_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.
fs_rename is provided by the Mcp Ssh Tool MCP server (skot/mcp-ssh-tool). 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 →