ingest_new_files | PolicyLayer

WHAT IT DOES

What ingest_new_files does on Hammerspace Storage Management MCP Server

AI agents invoke ingest_new_files to trigger actions in Hammerspace Storage Management MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why ingest_new_files needs a policy

This tool executes an automated ingestion pipeline that modifies file metadata (tagging) and moves files to a specific storage tier. It spans Write and Execute categories; since it triggers an external multi-step operation with side effects (tagging + tier management) and potentially invokes Kubernetes-based ingestion workflows with Milvus integration per the server description, Execute is the most appropriate…

From the tool's definition 'Ingest new files: find files with recent ctime/mtime, tag them, and place on Tier 1' — triggers a multi-step automated workflow: file discovery, tagging, and tier placement

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingest_new_files Rate-limited

ingest_new_files stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ingest_new_files": {
      "limits": [
        {
          "counter": "ingest_new_files_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 ingest_new_files

What does the ingest_new_files tool do? +

Ingest new files: find files with recent ctime/mtime, tag them, and place on Tier 1. It is categorised as a Execute tool in the Hammerspace Storage Management MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ingest_new_files? +

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

ingest_new_files is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ingest_new_files? +

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

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

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