Moves an object from one bucket to another or renames it within the same bucket by copying and deleting the original.
AI agents call move_object to permanently remove resources in Observability — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly deletes the original object after copying it, making the operation partially irreversible. If the copy step succeeds but the destination is unexpected, or if the delete occurs before confirmation, the original object is permanently removed. This qualifies as Destructive due to the irreversible deletion of the source object.
From the tool's definition Moves an object from one bucket to another or renames it within the same bucket by copying and deleting the original
Attacks that exploit this kind of access
Moves an object from one bucket to another or renames it within the same bucket by copying and deleting the original. It is categorised as a Destructive tool in the Observability MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Observability MCP server in PolicyLayer and add a rule for move_object: 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 Observability. Nothing to install.
move_object 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 move_object 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 move_object. 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.
move_object is provided by the Observability MCP server (@google-cloud/observability-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 →