Personal Agent Gateway: the user's OWN phone forwards an OTP/2FA code to the remote box so a redroid/device login that's blocked waiting for a code completes seamlessly — no gate id needed, no typing into a remote view. Matches the code to the oldest pending enter_code gate for that connector; a ...
AI agents call gateway_provide_otp to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | The OTP/2FA code the phone received |
connector | string | Yes | Connector id the code is for (e.g. 'misli') |
Parameters from the server's own tool schema.
Even though gateway_provide_otp only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
Personal Agent Gateway: the user's OWN phone forwards an OTP/2FA code to the remote box so a redroid/device login that's blocked waiting for a code completes seamlessly — no gate id needed, no typing into a remote view. Matches the code to the oldest pending enter_code gate for that connector; a code with no waiting login is a safe no-op. Does NOT bypass 2FA — it relays a code the user legitimately received; nothing is stored. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
gateway_provide_otp accepts 2 parameters: code, connector. Required: code, connector. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for gateway_provide_otp: 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.
gateway_provide_otp is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gateway_provide_otp 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 gateway_provide_otp. 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.
gateway_provide_otp 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.