blinks_confirmAction

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

High RISK CLASS

Category Execute

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/blinks-confirmaction.md

WHAT IT DOES

What blinks_confirmAction does on Sap

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

Parameter	Type	Required	Description
`actionUrl`	string	Yes	Action URL parameter for Blinks Confirm Action.
`signature`	string	Yes	Transaction signature after signing and submitting

Parameters from the server's own tool schema.

RISK

Why blinks_confirmAction is rated High

Confirms a Solana blockchain action by submitting a transaction signature to an external provider.

From the tool's definition sending the tx signature back to the Action provider

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blinks_confirmAction safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blinks_confirmAction, this is the rule to start with:

blinks_confirmAction Rate-limited

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about blinks_confirmAction

What does the blinks_confirmAction tool do? +

Confirm a completed Solana Action by sending the tx signature back to the Action provider. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does blinks_confirmAction accept? +

blinks_confirmAction accepts 2 parameters: actionUrl, signature. Required: actionUrl, signature. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on blinks_confirmAction? +

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

What risk level is blinks_confirmAction? +

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

Can I rate-limit blinks_confirmAction? +

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

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

blinks_confirmAction is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 375 Sap tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →