gateway_connect_finish · Yaver MCP: Risk & Policy

WHAT IT DOES

What gateway_connect_finish does on Yaver

AI agents use gateway_connect_finish to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

PARAMETERS

Parameter	Type	Required	Description
`code`	string	—	Authorization code to paste (headless fallback). Omit to wait for the loopback callback.
`connect_id`	string	Yes	The connect_id returned by gateway_connect

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why gateway_connect_finish needs a policy

An AI agent can call gateway_connect_finish faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gateway_connect_finish Rate-limited

gateway_connect_finish 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gateway_connect_finish": {
      "limits": [
        {
          "counter": "gateway_connect_finish_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about gateway_connect_finish

What does the gateway_connect_finish tool do? +

Personal Agent Gateway: complete a pending OAuth connector authoring (from gateway_connect). With no code it waits for the browser loopback callback; otherwise pass the pasted authorization code (headless boxes). Exchanges the code for tokens, stores them in your vault, and registers the connector. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does gateway_connect_finish accept? +

gateway_connect_finish accepts 2 parameters: code, connect_id. Required: connect_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gateway_connect_finish? +

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

What risk level is gateway_connect_finish? +

gateway_connect_finish is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gateway_connect_finish? +

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

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

gateway_connect_finish is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.