Get tags for a path from Hammerspace API
AI agents call get_tags 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 metadata (tags) associated with a storage path without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk—the worst-case scenario is information disclosure of existing tag metadata, which is low severity.
From the tool's definition Tool name 'get_tags' and description 'Get tags for a path from Hammerspace API' both indicate a retrieval operation. The verb 'Get' and the lack of any modification language confirm this is a query-only operation.
Attacks that exploit this kind of access
Get tags for a path from Hammerspace API. 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 get_tags: 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.
get_tags 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 get_tags 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 get_tags. 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.
get_tags 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 →