set_file_tag · Hammerspace Storage Management MCP Server MCP

WHAT IT DOES

What set_file_tag does on Hammerspace Storage Management MCP Server

AI agents use set_file_tag 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 set_file_tag needs a policy

The tool modifies file tags (metadata) using HSTK without deleting or destroying data. Tags can be changed, removed, or updated, making this a reversible Write operation rather than Destructive. Severity is medium because unauthorized tagging could misclassify files, affecting storage tiering, access controls, or data organization, but the operation itself is non-destructive and reversible.

From the tool's definition Tool name 'set_file_tag' and description 'Set a tag on a file' indicate modification of file metadata. This is a write operation that creates or modifies metadata reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_file_tag Rate-limited

set_file_tag 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": {
    "set_file_tag": {
      "limits": [
        {
          "counter": "set_file_tag_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 set_file_tag

What does the set_file_tag tool do? +

Set a tag on a file 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.

How do I enforce a policy on set_file_tag? +

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

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

Can I rate-limit set_file_tag? +

Yes. Add a rate_limit block to the set_file_tag 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 set_file_tag completely? +

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

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