从 .vibe-guard/tasks.json 返回下一个未阻塞的待处理任务。
AI agents call vguard_next_task to retrieve information from Vibe Guard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and returns task data from a JSON file (.vibe-guard/tasks.json) without modifying any state. It is a pure retrieval operation with no side effects.
From the tool's definition 返回下一个未阻塞的待处理任务 (returns the next unblocked pending task)
Attacks that exploit this kind of access
从 .vibe-guard/tasks.json 返回下一个未阻塞的待处理任务。. It is categorised as a Read tool in the Vibe Guard MCP Server, which means it retrieves data without modifying state.
Register the Vibe Guard MCP server in PolicyLayer and add a rule for vguard_next_task: 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_next_task is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vguard_next_task 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_next_task. 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_next_task 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 →