Restore project source to a previous version
AI agents use restore_source_version to create or update resources in Prowpt MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prowpt MCP Server environment.
Restoring source code is a state-changing operation that modifies project files, but it is not destructive because the previous state remains recoverable and the change can be undone by restoring to another version.
From the tool's definition Tool description states 'Restore project source to a previous version' — this modifies project source code by reverting it to a prior state. The action is reversible (can restore to a different version again), distinguishing it from destructive deletion.
Attacks that exploit this kind of access
Restore project source to a previous version. It is categorised as a Write tool in the Prowpt MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for restore_source_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 Prowpt MCP Server. Nothing to install.
restore_source_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_source_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_source_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_source_version is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). 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 →