tag_directory_recursive

WHAT IT DOES

What tag_directory_recursive does on Hammerspace Storage Management MCP Server

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

This tool modifies metadata (tags) on potentially a large number of files across an entire directory tree recursively. It is a Write operation as tagging is generally reversible (tags can be removed), but the blast radius is high because a single call can affect thousands of files across a recursive directory structure, making mistakes difficult to manually undo at scale.

From the tool's definition Tag all files in a directory recursively with a specified tag

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tag_directory_recursive Rate-limited

tag_directory_recursive 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": {
    "tag_directory_recursive": {
      "limits": [
        {
          "counter": "tag_directory_recursive_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 tag_directory_recursive

What does the tag_directory_recursive tool do? +

Tag all files in a directory recursively with a specified tag. 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 tag_directory_recursive? +

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

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

Can I rate-limit tag_directory_recursive? +

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

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

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