magicblock_ensureCrank

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

High RISK CLASS

Category Execute

Parameters 31 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/magicblock-ensurecrank.md

WHAT IT DOES

What magicblock_ensureCrank does on Sap

AI agents invoke magicblock_ensureCrank 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
`mint`	string	Yes	SPL mint to crank the transfer queue for
`cluster`	string	—	Cluster: 'mainnet', 'devnet', or custom RPC URL
`validator`	string	—	Optional ER validator pubkey. Defaults to the well-known MagicBlock validator (MAS1Dt9qreoRMQ14YQuhg8UTZMMzDdKhmkZMECCzk57)

Parameters from the server's own tool schema.

RISK

Why magicblock_ensureCrank is rated High

Triggers external blockchain delivery operation; despite read-only claim, it executes a queued fund transfer.

From the tool's definition forces one crank attempt, triggers the existing queued delivery

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs magicblock_ensureCrank 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_ensureCrank, this is the rule to start with:

magicblock_ensureCrank Rate-limited

magicblock_ensureCrank 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": {
    "magicblock_ensureCrank": {
      "limits": [
        {
          "counter": "magicblock_ensurecrank_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 magicblock_ensureCrank call is checked against it from then on.

FAQ

Questions about magicblock_ensureCrank

What does the magicblock_ensureCrank tool do? +

Force a transfer queue crank attempt for a mint. Use this after a private transfer or private swap if the Hydra delivery crank has not yet delivered funds to the recipient. The API verifies the validator-scoped transfer queue and forces one crank attempt, returning the crank signature. Read-only tier: this does not move funds, it triggers the existing queued delivery.. 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.

What parameters does magicblock_ensureCrank accept? +

magicblock_ensureCrank accepts 3 parameters: mint, cluster, validator. Required: mint. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on magicblock_ensureCrank? +

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

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

Can I rate-limit magicblock_ensureCrank? +

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

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

magicblock_ensureCrank 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 →