List all objectives using HSTK
AI agents call list_objectives to retrieve information from Hammerspace Storage Management MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing objectives from Hammerspace storage management without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries the current state of objectives. No blast radius from misuse—an AI agent listing objectives cannot cause harm beyond potential information disclosure of non-sensitive metadata.
From the tool's definition Tool name 'list_objectives' and description 'List all objectives' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all objectives using HSTK. It is categorised as a Read tool in the Hammerspace Storage Management MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hammerspace Storage Management MCP Server MCP server in PolicyLayer and add a rule for list_objectives: 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.
list_objectives is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_objectives 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 list_objectives. 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.
list_objectives 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 →