vibecontrols_auth_complete
Check if the user has completed the device code authorization in their browser. Call this after the user has opened the verification URL and entered the code from vibecontrols_auth_login. Returns "pending" if not yet authorized, "authenticated" on success.
This record as markdown: /tools/vibecontrols-mcp/vibecontrols-auth-complete.md
What vibecontrols_auth_complete does on Vibecontrols
AI agents use vibecontrols_auth_complete to create or update resources in Vibecontrols, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibecontrols environment.
Why vibecontrols_auth_complete is rated Medium
An AI agent can call vibecontrols_auth_complete faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs vibecontrols_auth_complete 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_auth_complete, this is the rule to start with:
vibecontrols_auth_complete stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_auth_complete call is checked against it from then on.
Questions about vibecontrols_auth_complete
Check if the user has completed the device code authorization in their browser. Call this after the user has opened the verification URL and entered the code from vibecontrols_auth_login. Returns "pending" if not yet authorized, "authenticated" on success. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_auth_complete: 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.
vibecontrols_auth_complete is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vibecontrols_auth_complete 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 vibecontrols_auth_complete. 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.
vibecontrols_auth_complete 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.
More on Vibecontrols, and thousands of servers like it.
This server
Across the catalogue