Remove a Hammerspace objective using the hs CLI
AI agents call remove_hs_objective to permanently remove resources in Hammerspace Storage Management MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a storage objective is a destructive operation that deletes a configuration entity governing storage tier management and file placement policies. This cannot be undone without recreating the objective, and misuse could affect how files are stored or tiered across the cluster, potentially impacting data availability and performance at scale.
From the tool's definition 'Remove a Hammerspace objective using the hs CLI' — 'remove' indicates irreversible deletion of a storage objective configuration
Attacks that exploit this kind of access
Remove a Hammerspace objective using the hs CLI. It is categorised as a Destructive tool in the Hammerspace Storage Management MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hammerspace Storage Management MCP Server MCP server in PolicyLayer and add a rule for remove_hs_objective: 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 Hammerspace Storage Management MCP Server. Nothing to install.
remove_hs_objective 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_hs_objective 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_hs_objective. 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_hs_objective is provided by the Hammerspace Storage Management MCP Server MCP server (mbloomhammerspace/mcp-1.5-main). 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 →