チェックサムファイルに基づいてディレクトリの整合性を検証します
AI agents call verify_directory_integrity 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 only reads checksum files and compares them against the current directory state to report on integrity status. It does not modify files, execute code, delete data, or move money. The operation is observational and produces no side effects beyond returning verification results, making it a standard Read operation.
From the tool's definition 'チェックサムファイルに基づいてディレクトリの整合性を検証します' (Verify directory integrity based on checksum files). The description indicates the tool verifies/validates existing data by comparing checksums—a read-only operation with no modification or side effects.
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 verify_directory_integrity: 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.
verify_directory_integrity 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 verify_directory_integrity 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 verify_directory_integrity. 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.
verify_directory_integrity 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 →