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

3land_listForSale

List an NFT for sale on 3.Land in any SPL token. 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...

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

What 3land_listForSale does on Sap

AI agents use 3land_listForSale 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
mint string Yes NFT mint to list
price string Yes Listing price (in specified token)
expiry string ISO 8601 listing expiry timestamp
seller string Yes Solana public key (base58)
priceMint string NFT mint address (base58)

Parameters from the server's own tool schema.

Why 3land_listForSale is rated Medium

Creates a marketplace listing, a reversible but significant on-chain write operation.

From the tool's definition List an NFT for sale on 3.Land in any SPL token

Questions about 3land_listForSale

What does the 3land_listForSale tool do? +

List an NFT for sale on 3.Land in any SPL token. 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: read/discovery 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 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 3land_listForSale accept? +

3land_listForSale accepts 5 parameters: mint, price, expiry, seller, priceMint. Required: mint, price, seller. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on 3land_listForSale? +

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

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

Can I rate-limit 3land_listForSale? +

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

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

3land_listForSale 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.