Run all VibeCoder quality gates (type safety, lint, security, bundle, deps, structure) and return a scored build report with letter grade (S/A/B/C/D/F). Perfect for vibe coders who want to know their build quality at a glance.
AI agents invoke vibe_check to trigger actions in VibeServe. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a suite of code analysis and quality gate processes rather than simply reading static data. Running lint, security scans, and bundle analysis involves executing tooling against the codebase. While it appears read-only in intent (reporting/scoring), it actively triggers external processes whose side effects depend on the codebase state.
From the tool's definition 'Run all VibeCoder quality gates (type safety, lint, security, bundle, deps, structure)' — the tool actively executes multiple analysis pipelines (linting, security scanning, dependency checks, bundle analysis) against a codebase.
Attacks that exploit this kind of access
Run all VibeCoder quality gates (type safety, lint, security, bundle, deps, structure) and return a scored build report with letter grade (S/A/B/C/D/F). Perfect for vibe coders who want to know their build quality at a glance. It is categorised as a Execute tool in the VibeServe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the VibeServe MCP server in PolicyLayer and add a rule for vibe_check: 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_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vibe_check 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_check. 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_check 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 →