执行平衡模式同类项目调研,并写入 .vibe-guard/research.md。
AI agents use vguard_prior_art to create or update resources in Vibe Guard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibe Guard environment.
The tool performs prior art research (Read) but its primary output is writing the results to a file (.vibe-guard/research.md). Since Write is more severe than Read, and the tool clearly states it writes to a file, it is classified as Write. Severity is medium because it creates/overwrites a project file which could affect downstream tasks but is reversible.
From the tool's definition 写入 .vibe-guard/research.md — explicitly writes research results to a file
Attacks that exploit this kind of access
执行平衡模式同类项目调研,并写入 .vibe-guard/research.md。. It is categorised as a Write tool in the Vibe Guard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vibe Guard MCP server in PolicyLayer and add a rule for vguard_prior_art: 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 Vibe Guard. Nothing to install.
vguard_prior_art 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 vguard_prior_art 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 vguard_prior_art. 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.
vguard_prior_art is provided by the Vibe Guard MCP server (sikuai2333/vibe-guard). 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 →