AI agents call vibe_health 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 reads and returns health/status information about the system. This is a read-only operation with no data modification, execution, or destructive potential. Low severity because misuse would only expose internal system metrics.
From the tool's definition "System health stats" — retrieves status/metrics with no side effects
Attacks that exploit this kind of access
System health stats. 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_health: 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_health 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_health 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_health. 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_health 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 →