複数の暗号化ファイルを一括復号化します
AI agents invoke decrypt_multiple_files to trigger actions in Claude MCP Server Integration. 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.
This tool performs bulk decryption of encrypted files, which is an execution operation that processes and transforms files. Decryption can expose sensitive data at scale and could be misused to access protected content. It is not purely a read operation as it actively transforms encrypted files, and not purely destructive (original encrypted files may remain).
From the tool's definition decrypt_multiple_files / 複数の暗号化ファイルを一括復号化します (batch decrypt multiple encrypted files)
Attacks that exploit this kind of access
複数の暗号化ファイルを一括復号化します. It is categorised as a Execute tool in the Claude MCP Server Integration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for decrypt_multiple_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 Claude MCP Server Integration. Nothing to install.
decrypt_multiple_files is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the decrypt_multiple_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.
Set action: deny in the PolicyLayer policy for decrypt_multiple_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.
decrypt_multiple_files 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 →