metaplex-nft_revokeAuthority

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

Critical RISK CLASS

Category Destructive

Parameters 33 required

Recommended Hiddensee 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-revokeauthority.md

WHAT IT DOES

What metaplex-nft_revokeAuthority does on Sap

AI agents call metaplex-nft_revokeAuthority to permanently remove resources in Sap, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`mint`	string	Yes	NFT mint address (base58)
`authority`	string	Yes	Current authority holder
`authorityType`	string	Yes	Authority Type parameter for Metaplex-nft Revoke Authority.

Parameters from the server's own tool schema.

RISK

Why metaplex-nft_revokeAuthority is rated Critical

Irreversibly removes NFT authority; cannot be undone and affects ownership/control permanently.

From the tool's definition Revoke (remove) authority. Irreversible for some types.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

metaplex-nft_revokeAuthority Hidden

metaplex-nft_revokeAuthority is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "metaplex-nft_revokeAuthority"
  ]
}

RESTRICT 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_revokeAuthority call is checked against it from then on.

FAQ

Questions about metaplex-nft_revokeAuthority

What does the metaplex-nft_revokeAuthority tool do? +

Revoke (remove) a specific authority. Irreversible for some types. 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 Destructive tool in the Sap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does metaplex-nft_revokeAuthority accept? +

metaplex-nft_revokeAuthority accepts 3 parameters: mint, authority, authorityType. Required: mint, authority, authorityType. The full parameter table on this page comes from the server's own tool schema.

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

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

metaplex-nft_revokeAuthority is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit metaplex-nft_revokeAuthority? +

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

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

metaplex-nft_revokeAuthority 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →