Create an objective using HSTK
AI agents use create_objective 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.
Creating an objective in a storage management system is a write operation that modifies configuration state but is reversible (objectives can be updated or deleted by other tools). It does not directly execute arbitrary commands, delete data irreversibly, or move funds.
From the tool's definition Tool description indicates 'Create an objective' which is a reversible write operation. Context shows this is part of a storage management system where objectives likely define policies (tier management, tagging rules, ingestion workflows).
Attacks that exploit this kind of access
Create an objective using HSTK. 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.
Register the Hammerspace Storage Management MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_objective is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →