remove_objective_from_path

WHAT IT DOES

What remove_objective_from_path does on Hammerspace Storage Management MCP Server

AI agents use remove_objective_from_path to create or update resources in Hammerspace Storage Management MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hammerspace Storage Management MCP Server environment.

WHY IT NEEDS A POLICY

Why remove_objective_from_path needs a policy

Removing an objective from a path changes the storage configuration/policy applied to that path. This is a reversible write operation (the objective can be re-applied), but it could have significant operational impact if storage tiering, data placement, or lifecycle policies are disrupted. It modifies configuration state rather than deleting data, so Write is appropriate rather than Destructive.

From the tool's definition 'Remove a Hammerspace objective from a path' — removes/detaches a storage management policy (objective) from a path

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_objective_from_path Rate-limited

remove_objective_from_path stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_objective_from_path": {
      "limits": [
        {
          "counter": "remove_objective_from_path_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hammerspace Storage Management MCP Server, so you can run agents against it safely.

FAQ

Questions about remove_objective_from_path

What does the remove_objective_from_path tool do? +

Remove a Hammerspace objective from a path. It is categorised as a Write tool in the Hammerspace Storage Management MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_objective_from_path? +

Register the Hammerspace Storage Management MCP Server MCP server in PolicyLayer and add a rule for remove_objective_from_path: 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.

What risk level is remove_objective_from_path? +

remove_objective_from_path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_objective_from_path? +

Yes. Add a rate_limit block to the remove_objective_from_path 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.

How do I block remove_objective_from_path completely? +

Set action: deny in the PolicyLayer policy for remove_objective_from_path. 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.

What MCP server provides remove_objective_from_path? +

remove_objective_from_path 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.