ストレージの無駄遣いを分析します
AI agents call analyze_storage_waste to retrieve information from Claude MCP Server Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs analysis and reporting on storage metrics—a pure read operation with no side effects. It retrieves or queries storage information to identify inefficiencies but does not create, modify, delete, or execute operations. The 'analyze' prefix aligns with the sibling tools (analyze_code_performance, analyze_file_activity, etc.) which are all informational queries.
From the tool's definition Tool name 'analyze_storage_waste' and description 'ストレージの無駄遣いを分析します' (analyzes storage waste) indicate a read-only operation that examines and reports on storage usage patterns without modifying any data.
Attacks that exploit this kind of access
ストレージの無駄遣いを分析します. It is categorised as a Read tool in the Claude MCP Server Integration MCP Server, which means it retrieves data without modifying state.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for analyze_storage_waste: 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 Claude MCP Server Integration. Nothing to install.
analyze_storage_waste is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze_storage_waste 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.
Set action: deny in the PolicyLayer policy for analyze_storage_waste. 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.
analyze_storage_waste is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →