AI agents use ftp_rollback to create or update resources in Ftp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ftp environment.
ftp_rollback restores files from a snapshot, which is a write/overwrite operation on the remote filesystem. While framed as a safety mechanism, it overwrites current file contents with a prior state — this is a reversible write (you could roll forward again) rather than a destruction of data. However, misuse could overwrite important changes made since the snapshot, giving it a high severity blast radius.
From the tool's definition Undo a previous file mutation by restoring it from a system-generated snapshot
Attacks that exploit this kind of access
Undo a previous file mutation by restoring it from a system-generated snapshot. This provides safety during complex refactoring tasks. It is categorised as a Write tool in the Ftp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ftp MCP server in PolicyLayer and add a rule for ftp_rollback: 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 Ftp. Nothing to install.
ftp_rollback 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 ftp_rollback 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 ftp_rollback. 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.
ftp_rollback is provided by the Ftp MCP server (kynlos/ftp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ftp_rollback is one line of Ftp's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →