blinks_getAction
Fetch metadata for a Solana Action (Blink) — returns title, description, available actions, and parameters. 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 signin...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/blinks-getaction.md
What blinks_getAction does on Sap
AI agents call blinks_getAction to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
actionUrl | string | Yes | Solana Action URL (https endpoint implementing the Actions spec) |
Parameters from the server's own tool schema.
Why blinks_getAction is rated Low
Tool retrieves metadata and validates action parameters without modifying data or executing transactions.
From the tool's definition Fetch metadata for a Solana Action (Blinks) — returns title, description, available actions, and parameters.
Attacks that exploit this kind of access
The rule that runs blinks_getAction 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_getAction, this is the rule to start with:
blinks_getAction is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every blinks_getAction call is checked against it from then on.
Questions about blinks_getAction
Fetch metadata for a Solana Action (Blink) — returns title, description, available actions, and parameters. 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: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
blinks_getAction accepts 1 parameter: actionUrl. Required: actionUrl. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for blinks_getAction: 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.
blinks_getAction 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 blinks_getAction 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 blinks_getAction. 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.
blinks_getAction 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.
More on Sap, and thousands of servers like it.
This server
Across the catalogue