Low Risk

analyze_storage

[MONITORING] Unified storage analysis tool. Actions: disk_usage (check disk space for critical paths), cache_stats (analyze pacman package cache). Works on any system for disk_usage, Arch only for cache_stats.

How to control analyze_storage ↓

AI agents call analyze_storage to retrieve information from Arch Linux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

analyze_storage performs read-only diagnostic operations: disk_usage queries filesystem space metrics, and cache_stats analyzes existing cache data. Neither action modifies, executes, or deletes anything. This is a pure monitoring/observability tool with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description explicitly tags as [MONITORING] and lists actions as 'check disk space' and 'analyze' — both informational operations with no side effects. No creation, modification, deletion, or execution of commands.

Documented attack patterns abuse exactly the kind of access analyze_storage gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Arch Linux, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_storage:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_storage": {}
  }
}

analyze_storage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Arch Linux — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the analyze_storage tool do? +

[MONITORING] Unified storage analysis tool. Actions: disk_usage (check disk space for critical paths), cache_stats (analyze pacman package cache). Works on any system for disk_usage, Arch only for cache_stats. It is categorised as a Read tool in the Arch Linux MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_storage? +

Register the Arch Linux MCP server in PolicyLayer and add a rule for analyze_storage: 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 Arch Linux. Nothing to install.

What risk level is analyze_storage? +

analyze_storage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyze_storage? +

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

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

analyze_storage is provided by the Arch Linux MCP server (nihalxkumar/arch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Arch Linux tool call.

Deterministic rules across all 22 Arch Linux tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

22 Arch Linux tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.