Remove a backend from the manager.
AI agents call remove_backend to permanently remove resources in Omni Fs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a backend is a destructive action that irreversibly deletes the configuration linking the system to an entire file system (local, S3, WebDAV, etc.). This blocks access to potentially critical storage and cannot be easily recovered. While not data deletion per se, it destroys the operational configuration of a storage backend, which qualifies as Destructive rather than Write (which is reversible).
From the tool's definition Tool name 'remove_backend' with description 'Remove a backend from the manager' indicates irreversible deletion of a configured file system backend. This prevents further access to that backend's storage and cannot be undone without re-registration.
Attacks that exploit this kind of access
Remove a backend from the manager. It is categorised as a Destructive tool in the Omni Fs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Omni Fs MCP server in PolicyLayer and add a rule for remove_backend: 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 Omni Fs. Nothing to install.
remove_backend is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_backend 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 remove_backend. 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.
remove_backend is provided by the Omni Fs MCP server (vaayne/omni-fs-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 →