magicblock_isMintInitialized
Check whether a mint has a validator-scoped transfer queue on the ephemeral RPC.. 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; ca...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/magicblock-ismintinitialized.md
What magicblock_isMintInitialized does on Sap
AI agents call magicblock_isMintInitialized 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 |
|---|---|---|---|
mint | string | Yes | SPL mint to check |
cluster | string | — | Cluster: 'mainnet', 'devnet', or custom RPC URL |
validator | string | — | Optional ER validator pubkey |
Parameters from the server's own tool schema.
Why magicblock_isMintInitialized is rated Low
Tool queries blockchain state without modifying data or causing side effects.
From the tool's definition Check whether a mint has a validator-scoped transfer queue.
Attacks that exploit this kind of access
The rule that runs magicblock_isMintInitialized 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_isMintInitialized, this is the rule to start with:
magicblock_isMintInitialized 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 magicblock_isMintInitialized call is checked against it from then on.
Questions about magicblock_isMintInitialized
Check whether a mint has a validator-scoped transfer queue on the ephemeral RPC.. 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 Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
magicblock_isMintInitialized accepts 3 parameters: mint, cluster, validator. Required: mint. 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_isMintInitialized: 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_isMintInitialized 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 magicblock_isMintInitialized 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_isMintInitialized. 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_isMintInitialized 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