vibecontrols_configuration_security_run_scan

Trigger a security scan for a vibe at a specific stage.

SERVERVibecontrols SOURCE@vibecontrols/mcp

High RISK CLASS

Category Execute

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-configuration-security-run-scan.md

WHAT IT DOES

What vibecontrols_configuration_security_run_scan does on Vibecontrols

AI agents invoke vibecontrols_configuration_security_run_scan to trigger actions in Vibecontrols. 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.

Parameter	Type	Required	Description
`stage`	string	Yes
`vibeId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why vibecontrols_configuration_security_run_scan is rated High

vibecontrols_configuration_security_run_scan triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_configuration_security_run_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_configuration_security_run_scan, this is the rule to start with:

vibecontrols_configuration_security_run_scan Rate-limited

vibecontrols_configuration_security_run_scan 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": {
    "vibecontrols_configuration_security_run_scan": {
      "limits": [
        {
          "counter": "vibecontrols_configuration_security_run_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_configuration_security_run_scan call is checked against it from then on.

FAQ

Questions about vibecontrols_configuration_security_run_scan

What does the vibecontrols_configuration_security_run_scan tool do? +

Trigger a security scan for a vibe at a specific stage. It is categorised as a Execute tool in the Vibecontrols MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does vibecontrols_configuration_security_run_scan accept? +

vibecontrols_configuration_security_run_scan accepts 2 parameters: stage, vibeId. Required: stage, vibeId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_configuration_security_run_scan? +

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

What risk level is vibecontrols_configuration_security_run_scan? +

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

Can I rate-limit vibecontrols_configuration_security_run_scan? +

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

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

vibecontrols_configuration_security_run_scan is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP →editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →