ファイルを特定バージョンに復元します
AI agents use restore_file_version to create or update resources in Claude MCP Server Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude MCP Server Integration environment.
The tool modifies file content by restoring to a prior version. While this is not strictly destructive (it can be undone by restoring to another version), it is a write operation that changes data. Severity is high because restoring wrong versions could corrupt project state or lose recent work, and the risk depends on which version is restored.
From the tool's definition Tool name 'restore_file_version' and description stating it 'restores a file to a specific version' indicates modification of file state to a previous state.
Attacks that exploit this kind of access
ファイルを特定バージョンに復元します. It is categorised as a Write tool in the Claude MCP Server Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for restore_file_version: 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.
restore_file_version is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_file_version 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 restore_file_version. 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.
restore_file_version 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 →