sap_sns_build_manage_record_transaction

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

High RISK CLASS

Category Execute

Parameters 40 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/sap-sns-build-manage-record-transaction.md

WHAT IT DOES

What sap_sns_build_manage_record_transaction does on Sap

AI agents invoke sap_sns_build_manage_record_transaction to trigger actions in Sap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`owner`	string	—	The Solana public key (base58) of the domain owner authorizing the record change
`value`	string \| null	—	The new record value as a string, or null to delete the record
`domain`	string	—	The .sol domain name whose record should be created, updated, or deleted
`recordType`	string	—	The SNS record type to manage (e.g. TXT, Url, IPFS, ETH, BTC, etc.)

Parameters from the server's own tool schema.

RISK

Why sap_sns_build_manage_record_transaction is rated High

sap_sns_build_manage_record_transaction triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_sns_build_manage_record_transaction Rate-limited

sap_sns_build_manage_record_transaction stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_sns_build_manage_record_transaction": {
      "limits": [
        {
          "counter": "sap_sns_build_manage_record_transaction_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sap_sns_build_manage_record_transaction

What does the sap_sns_build_manage_record_transaction tool do? +

Temporarily unavailable. SAP MCP does not currently publish an SNS record write builder because the historical Bonfida SNS npm package is not installable from npmjs. The tool fails fast before payment or signing. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: hosted-safe builder. If a transaction is returned, preview/sign/submit with sap_payments_finalize_transaction; never create temporary signing scripts. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does sap_sns_build_manage_record_transaction accept? +

sap_sns_build_manage_record_transaction accepts 4 parameters: owner, value, domain, recordType. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_sns_build_manage_record_transaction? +

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

sap_sns_build_manage_record_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sap_sns_build_manage_record_transaction? +

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

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

sap_sns_build_manage_record_transaction 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 → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →