Bucket object operations: list objects, upload, get download URL, or delete objects
AI agents call liara_manage_bucket_objects to permanently remove resources in Liara MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool spans multiple categories including Read (list objects), Write (upload), and Destructive (delete objects). Per the rules, the most severe applicable category must be chosen. Since deletion of bucket objects is irreversible, this tool is classified as Destructive. The blast radius is high because an AI agent could permanently delete objects from cloud storage buckets.
From the tool's definition 'delete objects' is explicitly listed as one of the operations this tool can perform
Documented attack patterns abuse exactly the kind of access liara_manage_bucket_objects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Liara MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for liara_manage_bucket_objects:
{
"version": "1",
"default": "deny",
"hide": [
"liara_manage_bucket_objects"
]
} liara_manage_bucket_objects disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Bucket object operations: list objects, upload, get download URL, or delete objects. It is categorised as a Destructive tool in the Liara MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Liara MCP Server MCP server in PolicyLayer and add a rule for liara_manage_bucket_objects: 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 Liara MCP Server. Nothing to install.
liara_manage_bucket_objects 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 liara_manage_bucket_objects 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 liara_manage_bucket_objects. 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.
liara_manage_bucket_objects is provided by the Liara MCP Server MCP server (razavioo/liara-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Liara MCP Server, 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.
108 Liara MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.