metaplex-nft_delegateAuthority

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

Medium RISK CLASS

Category Write

Parameters 44 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/metaplex-nft-delegateauthority.md

WHAT IT DOES

What metaplex-nft_delegateAuthority does on Sap

AI agents use metaplex-nft_delegateAuthority 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.

Parameter	Type	Required	Description
`mint`	string	Yes	NFT mint address (base58)
`newAuthority`	string	Yes	Solana public key (base58)
`authorityType`	string	Yes	Type of authority to delegate
`currentAuthority`	string	Yes	Solana public key (base58)

Parameters from the server's own tool schema.

RISK

Why metaplex-nft_delegateAuthority is rated Medium

Modifies NFT authority ownership reversibly; high blast radius if delegated to adversary.

From the tool's definition Delegate authority (update, mint, freeze, collection) to another wallet.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

metaplex-nft_delegateAuthority Rate-limited

metaplex-nft_delegateAuthority stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "metaplex-nft_delegateAuthority": {
      "limits": [
        {
          "counter": "metaplex-nft_delegateauthority_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every metaplex-nft_delegateAuthority call is checked against it from then on.

FAQ

Questions about metaplex-nft_delegateAuthority

What does the metaplex-nft_delegateAuthority tool do? +

Delegate a specific authority (update, mint, freeze, collection) to another wallet. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. 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: 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 metaplex-nft_delegateAuthority accept? +

metaplex-nft_delegateAuthority accepts 4 parameters: mint, newAuthority, authorityType, currentAuthority. Required: mint, newAuthority, authorityType, currentAuthority. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on metaplex-nft_delegateAuthority? +

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

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

Can I rate-limit metaplex-nft_delegateAuthority? +

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

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

metaplex-nft_delegateAuthority 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →