Merge official new version with custom changes
AI agents use svc_merge to create or update resources in Skill Vision Control (SVC) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Skill Vision Control (SVC) environment.
This tool creates or modifies skill version data by merging official updates with custom local modifications. Merge operations write changes to local state but are reversible via the rollback capability present on this server. The severity is medium because misconfigured merges could corrupt skill functionality or lose custom modifications, but the operation itself is non-destructive and can be undone.
From the tool's definition Tool name 'svc_merge' with description 'Merge official new version with custom changes' indicates modification of local skill data through a merge operation.
Documented attack patterns abuse exactly the kind of access svc_merge 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_merge:
{
"version": "1",
"default": "deny",
"tools": {
"svc_merge": {
"limits": [
{
"counter": "svc_merge_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}svc_merge stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Merge official new version with custom changes. It is categorised as a Write tool in the Skill Vision Control (SVC) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Skill Vision Control (SVC) MCP server in PolicyLayer and add a rule for svc_merge: 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_merge 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 svc_merge 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_merge. 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_merge 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.