gateway_act_confirm · Yaver MCP: Risk & Policy

WHAT IT DOES

What gateway_act_confirm does on Yaver

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

PARAMETERS

Parameter	Type	Required	Description
`act_id`	string	Yes	The act_id returned by gateway_act
`answer`	string	—	'approve' to execute; anything else declines

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why gateway_act_confirm needs a policy

gateway_act_confirm 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 Ready

Verdict

gateway_act_confirm Rate-limited

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

RATE-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_act_confirm

What does the gateway_act_confirm tool do? +

Personal Agent Gateway: confirm + execute a previously previewed act (from gateway_act dry-run). The confirm call IS the second key: answer 'approve' to execute, anything else declines. High/financial acts may additionally block on a tapped approval on your phone. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does gateway_act_confirm accept? +

gateway_act_confirm accepts 2 parameters: act_id, answer. Required: act_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gateway_act_confirm? +

Register the Yaver MCP server in PolicyLayer and add a rule for gateway_act_confirm: 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_act_confirm? +

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

Can I rate-limit gateway_act_confirm? +

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

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

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