vibe_benchmark · VibeServe MCP: Risk & Policy

WHAT IT DOES

What vibe_benchmark does on VibeServe

AI agents invoke vibe_benchmark 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.

WHY IT NEEDS A POLICY

Why vibe_benchmark needs a policy

This tool executes a benchmarking loop, which involves running code with side effects (CPU usage, potential resource consumption, timing measurements). While not destructive or financial, it triggers external computational operations whose resource impact depends on loop parameters. Classified as Execute rather than Read because it actively runs processes beyond simple querying.

From the tool's definition Tool name 'vibe_benchmark' combined with description 'Run a benchmarking loop with ASCII graphs' indicates execution of a computational loop/benchmark process. The verb 'Run' signals active code execution rather than data retrieval.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibe_benchmark Rate-limited

vibe_benchmark stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vibe_benchmark": {
      "limits": [
        {
          "counter": "vibe_benchmark_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches VibeServe, so you can run agents against it safely.

FAQ

Questions about vibe_benchmark

What does the vibe_benchmark tool do? +

Run a benchmarking loop with ASCII graphs. 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.

How do I enforce a policy on vibe_benchmark? +

Register the VibeServe MCP server in PolicyLayer and add a rule for vibe_benchmark: 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.

What risk level is vibe_benchmark? +

vibe_benchmark is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vibe_benchmark? +

Yes. Add a rate_limit block to the vibe_benchmark 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.

How do I block vibe_benchmark completely? +

Set action: deny in the PolicyLayer policy for vibe_benchmark. 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.

What MCP server provides vibe_benchmark? +

vibe_benchmark 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.