vibefix_diagnose · Vibefix MCP: Risk & Policy

WHAT IT DOES

What vibefix_diagnose does on Vibefix

AI agents invoke vibefix_diagnose to trigger actions in Vibefix. 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 vibefix_diagnose needs a policy

While the tool itself is read-only in terms of data retrieval (returns scores and issues), it executes a diagnostic scan—an external operation triggered by user-provided input (the URL). The tool depends on arguments to determine behavior and can trigger side effects through the target website interaction.

From the tool's definition The tool 'Run a free diagnostic scan on any public URL' performs an external operation (website diagnostics/scanning) whose effects and scope depend on the target URL argument provided by the user. This is an external trigger operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibefix_diagnose Rate-limited

vibefix_diagnose 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": {
    "vibefix_diagnose": {
      "limits": [
        {
          "counter": "vibefix_diagnose_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 Vibefix, so you can run agents against it safely.

FAQ

Questions about vibefix_diagnose

What does the vibefix_diagnose tool do? +

Run a free diagnostic scan on any public URL. Returns performance, accessibility, SEO, and best practices scores plus a list of issues found — each with a ready-made bounty pre-fill so the user can post a fix request in one click. No API key required. It is categorised as a Execute tool in the Vibefix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vibefix_diagnose? +

Register the Vibefix MCP server in PolicyLayer and add a rule for vibefix_diagnose: 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 Vibefix. Nothing to install.

What risk level is vibefix_diagnose? +

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

Can I rate-limit vibefix_diagnose? +

Yes. Add a rate_limit block to the vibefix_diagnose 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 vibefix_diagnose completely? +

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

vibefix_diagnose is provided by the Vibefix MCP server (vibefix-technologies/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.