sap_build_agent_update_transaction

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

Medium RISK CLASS

Category Write

Parameters 90 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-build-agent-update-transaction.md

WHAT IT DOES

What sap_build_agent_update_transaction does on Sap

AI agents use sap_build_agent_update_transaction 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
`name`	string	—	Optional replacement display name.
`agentId`	string	—	Optional replacement stable agent id.
`pricing`	array	—	Optional FULL replacement pricing tier list.
`agentUri`	string	—	Optional replacement public metadata URI (use for image updates after uploading to IPFS/etc).
`protocols`	array	—	Optional FULL replacement protocol list.
`description`	string	—	Optional replacement description.
`ownerWallet`	string	—	Agent owner wallet public key (base58) — sole required signer.
`capabilities`	array	—	Optional FULL replacement capability list.
`x402Endpoint`	string	—	Optional replacement x402 endpoint.

Parameters from the server's own tool schema.

RISK

Why sap_build_agent_update_transaction is rated Medium

Builds an unsigned transaction to update an agent, modifying on-chain state when signed.

From the tool's definition unsigned builder for update_agent; owner wallet signs locally after preview

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_build_agent_update_transaction Rate-limited

sap_build_agent_update_transaction 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": {
    "sap_build_agent_update_transaction": {
      "limits": [
        {
          "counter": "sap_build_agent_update_transaction_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 sap_build_agent_update_transaction call is checked against it from then on.

FAQ

Questions about sap_build_agent_update_transaction

What does the sap_build_agent_update_transaction tool do? +

Hosted-safe unsigned builder for update_agent. The owner wallet signs locally after preview; null fields are ignored on-chain. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile. 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: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. 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 sap_build_agent_update_transaction accept? +

sap_build_agent_update_transaction accepts 9 parameters: name, agentId, pricing, agentUri, protocols, description, ownerWallet, capabilities, x402Endpoint. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_build_agent_update_transaction? +

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

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

Can I rate-limit sap_build_agent_update_transaction? +

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

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

sap_build_agent_update_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 453 Sap tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_kill_agent on Team Manager MCP → The MCP Attack Database →

Guides

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