vibecontrols_sessions_transfer_control

Transfer control of a shared session to another collaborator.

SERVERVibecontrols SOURCE@vibecontrols/mcp

Critical RISK CLASS

Category Financial

Parameters 22 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-sessions-transfer-control.md

WHAT IT DOES

What vibecontrols_sessions_transfer_control does on Vibecontrols

AI agents use vibecontrols_sessions_transfer_control to commit financial operations through Vibecontrols, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`toUserId`	string	Yes	User ID to transfer control to
`sessionId`	string	Yes	Session ID

Parameters from the server's own tool schema.

RISK

Why vibecontrols_sessions_transfer_control is rated Critical

vibecontrols_sessions_transfer_control moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_sessions_transfer_control 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_sessions_transfer_control, this is the rule to start with:

vibecontrols_sessions_transfer_control Approval-gated

Any call to vibecontrols_sessions_transfer_control is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vibecontrols_sessions_transfer_control": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vibecontrols_sessions_transfer_control

What does the vibecontrols_sessions_transfer_control tool do? +

Transfer control of a shared session to another collaborator. It is categorised as a Financial tool in the Vibecontrols MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does vibecontrols_sessions_transfer_control accept? +

vibecontrols_sessions_transfer_control accepts 2 parameters: toUserId, sessionId. Required: toUserId, sessionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_sessions_transfer_control? +

Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_sessions_transfer_control: 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_sessions_transfer_control? +

vibecontrols_sessions_transfer_control is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit vibecontrols_sessions_transfer_control? +

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

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

vibecontrols_sessions_transfer_control 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 → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge →transfer_sites on A3plus →abs_zalo_transfer_owner on Abs Zalo Bot → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →