3land_mintAndList
Mint an NFT on 3.Land and automatically list it for sale. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair ma...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/3land-mintandlist.md
What 3land_mintAndList does on Sap
AI agents use 3land_mintAndList to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Name name or domain value used by 3land Mint And List. |
image | string | Yes | NFT image URL |
owner | string | Yes | Solana public key (base58) |
price | string | Yes | Listing price in token amount |
supply | number | — | Edition supply |
priceMint | string | — | NFT mint address (base58) |
attributes | array | — | Attributes parameter for 3land Mint And List. |
collection | string | Yes | 3.Land collection ID |
description | string | — | Description parameter for 3land Mint And List. |
Parameters from the server's own tool schema.
Why 3land_mintAndList is rated Critical
Minting and listing NFTs for sale involves financial transactions on a marketplace.
From the tool's definition Mint an NFT and automatically list it for sale
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs 3land_mintAndList 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 3land_mintAndList, this is the rule to start with:
Any call to 3land_mintAndList is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every 3land_mintAndList call is checked against it from then on.
Questions about 3land_mintAndList
Mint an NFT on 3.Land and automatically list it for sale. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
3land_mintAndList accepts 9 parameters: name, image, owner, price, supply, priceMint, attributes, collection, description. Required: name, image, owner, price, collection. 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 3land_mintAndList: 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.
3land_mintAndList is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 3land_mintAndList 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 3land_mintAndList. 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.
3land_mintAndList 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.
Across the catalogue