AI agents call vibe_score to retrieve information from VibeServe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves an existing build score value without triggering any execution or modification. The phrase 'without running a full check' reinforces that this is a passive read operation with no side effects.
From the tool's definition Get the latest build score without running a full check
Attacks that exploit this kind of access
Get the latest build score without running a full check. It is categorised as a Read tool in the VibeServe MCP Server, which means it retrieves data without modifying state.
Register the VibeServe MCP server in PolicyLayer and add a rule for vibe_score: 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_score 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 vibe_score 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_score. 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_score 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 →