magicblock_login
Exchange a signed challenge for a bearer token (step 2 of PER auth flow). The token is used for private-balance and private transfers.. 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 cann...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/magicblock-login.md
What magicblock_login does on Sap
AI agents invoke magicblock_login 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 |
|---|---|---|---|
pubkey | string | Yes | Wallet pubkey that signed the challenge |
cluster | string | — | Cluster: 'mainnet', 'devnet', or custom RPC URL |
challenge | string | Yes | Challenge string from magicblock_challenge |
signature | string | Yes | Wallet signature over the challenge string |
Parameters from the server's own tool schema.
Why magicblock_login is rated High
Authenticates and obtains a bearer token enabling private financial transfers on-chain.
From the tool's definition Exchange a signed challenge for a bearer token... private-balance and private transfers
Attacks that exploit this kind of access
The rule that runs magicblock_login 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 magicblock_login, this is the rule to start with:
magicblock_login 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every magicblock_login call is checked against it from then on.
Questions about magicblock_login
Exchange a signed challenge for a bearer token (step 2 of PER auth flow). The token is used for private-balance and private transfers.. 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 Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
magicblock_login accepts 4 parameters: pubkey, cluster, challenge, signature. Required: pubkey, challenge, signature. 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 magicblock_login: 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.
magicblock_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the magicblock_login 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 magicblock_login. 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.
magicblock_login 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