aiq_optimize_tiering | PolicyLayer

WHAT IT DOES

What aiq_optimize_tiering does on Hammerspace Storage Management MCP Server

AI agents invoke aiq_optimize_tiering 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 aiq_optimize_tiering needs a policy

Tier optimization involves automatically relocating data between storage tiers (e.g., hot, warm, cold), which constitutes a system-modifying operation. While not strictly destructive, it executes automated storage reconfiguration that can have significant side effects on performance and data placement.

From the tool's definition 'AI-powered tier optimization' and 'tier management' in server description — this tool actively moves/reassigns data across storage tiers using AI-driven decisions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aiq_optimize_tiering Rate-limited

aiq_optimize_tiering 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": {
    "aiq_optimize_tiering": {
      "limits": [
        {
          "counter": "aiq_optimize_tiering_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 aiq_optimize_tiering

What does the aiq_optimize_tiering tool do? +

AI-powered tier optimization using NVIDIA AIQ Toolkit. 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 aiq_optimize_tiering? +

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

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

Can I rate-limit aiq_optimize_tiering? +

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

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

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