sap_build_agent_lifecycle_transaction

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

High RISK CLASS

Category Execute

Parameters 20 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-lifecycle-transaction.md

WHAT IT DOES

What sap_build_agent_lifecycle_transaction does on Sap

AI agents invoke sap_build_agent_lifecycle_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
`action`	string	—	Lifecycle action to build.
`ownerWallet`	string	—	Agent owner wallet public key (base58) — sole required signer.

Parameters from the server's own tool schema.

RISK

Why sap_build_agent_lifecycle_transaction is rated High

Constructs and executes irreversible agent lifecycle transactions requiring owner wallet signature; potential for state changes and financial impact.

From the tool's definition deactivate_agent, reactivate_agent, close_agent, migrate_pricing_menu, unsigned builder

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_build_agent_lifecycle_transaction Rate-limited

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

FAQ

Questions about sap_build_agent_lifecycle_transaction

What does the sap_build_agent_lifecycle_transaction tool do? +

Hosted-safe unsigned builder for the agent lifecycle actions: deactivate_agent, reactivate_agent, close_agent (reclaims rent), and migrate_pricing_menu (one-time backfill of the PricingMenu PDA for agents registered before pricing menus existed). The owner wallet signs locally. 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 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_build_agent_lifecycle_transaction accept? +

sap_build_agent_lifecycle_transaction accepts 2 parameters: action, ownerWallet. 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_lifecycle_transaction? +

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

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

Can I rate-limit sap_build_agent_lifecycle_transaction? +

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

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

sap_build_agent_lifecycle_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 → 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 →