Rollback a skill to its previous version
AI agents call svc_rollback to permanently remove resources in Skill Vision Control (SVC) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Rolling back to a previous version replaces and discards the current version's state. While the server has versioning capabilities (implying some recovery may be possible via svc_switch_version), the rollback action itself overwrites current state and any unsaved/uncommitted modifications could be permanently lost. This makes it closer to Destructive than Write.
From the tool's definition 'Rollback a skill to its previous version' — reverting to a prior version overwrites the current version state, which is not trivially reversible without a separate backup or re-merge
Documented attack patterns abuse exactly the kind of access svc_rollback gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Skill Vision Control (SVC), and nothing reaches the server without passing your rules. This is the rule we recommend for svc_rollback:
{
"version": "1",
"default": "deny",
"hide": [
"svc_rollback"
]
}svc_rollback disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Rollback a skill to its previous version. It is categorised as a Destructive tool in the Skill Vision Control (SVC) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Skill Vision Control (SVC) MCP server in PolicyLayer and add a rule for svc_rollback: 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 Skill Vision Control (SVC). Nothing to install.
svc_rollback is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the svc_rollback 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 svc_rollback. 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.
svc_rollback is provided by the Skill Vision Control (SVC) MCP server (jane-xiaoer/skill-vision-control). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Skill Vision Control (SVC), add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Skill Vision Control (SVC) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.