New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

blinks_resolveBlinkUrl

Resolve a Blink URL (e.g. dial.to link) to its underlying Solana Action URL. 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 th...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Medium RISK CLASS
Category Write
Parameters 11 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-resolveblinkurl.md

What blinks_resolveBlinkUrl does on Sap

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

ParameterTypeRequiredDescription
blinkUrl string Yes Blink URL (e.g. https://dial.to/?action=solana-action:...)

Parameters from the server's own tool schema.

Why blinks_resolveBlinkUrl is rated Medium

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

Questions about blinks_resolveBlinkUrl

What does the blinks_resolveBlinkUrl tool do? +

Resolve a Blink URL (e.g. dial.to link) to its underlying Solana Action URL. 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: 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does blinks_resolveBlinkUrl accept? +

blinks_resolveBlinkUrl accepts 1 parameter: blinkUrl. Required: blinkUrl. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on blinks_resolveBlinkUrl? +

Register the Sap MCP server in PolicyLayer and add a rule for blinks_resolveBlinkUrl: 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_resolveBlinkUrl? +

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

Can I rate-limit blinks_resolveBlinkUrl? +

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

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

blinks_resolveBlinkUrl 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.