vguard_integration_run · Vibe Guard MCP: Risk & Policy

WHAT IT DOES

What vguard_integration_run does on Vibe Guard

AI agents invoke vguard_integration_run to trigger actions in Vibe Guard. 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 vguard_integration_run needs a policy

This tool executes integration initialization commands, which can trigger external operations and side effects depending on the arguments provided (integrations being initialized).

From the tool's definition Tool name contains 'run' and description states 'dry-run 或显式执行支持的集成初始化命令' (dry-run or explicitly execute supported integration initialization commands).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vguard_integration_run Rate-limited

vguard_integration_run 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": {
    "vguard_integration_run": {
      "limits": [
        {
          "counter": "vguard_integration_run_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 Vibe Guard, so you can run agents against it safely.

FAQ

Questions about vguard_integration_run

What does the vguard_integration_run tool do? +

dry-run 或显式执行支持的集成初始化命令。默认 dry-run。. It is categorised as a Execute tool in the Vibe Guard MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vguard_integration_run? +

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

What risk level is vguard_integration_run? +

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

Can I rate-limit vguard_integration_run? +

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

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

vguard_integration_run is provided by the Vibe Guard MCP server (sikuai2333/vibe-guard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.