AI agents use vibe_upgrade_design to create or update resources in VibeServe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VibeServe environment.
The tool upgrades (modifies) an existing design template, which constitutes a Write operation. It applies production patterns to a template, likely overwriting or updating it. Severity is medium because it modifies potentially important UI code/templates, though changes are likely reversible via version control.
From the tool's definition 'Upgrade a design template with senior-dev production patterns' — modifies/overwrites an existing design template
Attacks that exploit this kind of access
Upgrade a design template with senior-dev production patterns. It is categorised as a Write tool in the VibeServe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VibeServe MCP server in PolicyLayer and add a rule for vibe_upgrade_design: 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 VibeServe. Nothing to install.
vibe_upgrade_design 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 vibe_upgrade_design 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 vibe_upgrade_design. 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.
vibe_upgrade_design is provided by the VibeServe MCP server (ncsound919/vibeserve). 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 →