sap_update_agent

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-update-agent.md

WHAT IT DOES

What sap_update_agent does on Sap

AI agents use sap_update_agent 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. Omit to keep the current name.
`agentId`	string	—	Optional replacement stable agent id. Omit to keep current agentId.
`pricing`	array	—	Optional full replacement pricing tier list. Omit to keep current pricing.
`agentUri`	string	—	Optional replacement public URI for agent metadata/profile. Use this to update pictures after uploading metadata to IPFS, Arweave, Kommodo, or HTTPS.
`protocols`	array	—	Optional full replacement protocol list. Omit to keep current protocols.
`description`	string	—	Optional replacement description. Omit to keep the current description.
`metadataUri`	string	—	Alias for agentUri. Use a public metadata JSON URI; never use a desktop file path.
`capabilities`	array	—	Optional full replacement capability list. Omit to keep current capabilities; do not send only the new item unless replacing the whole list is intended.
`x402Endpoint`	string	—	Optional replacement x402 discovery/payment endpoint. Omit to keep current endpoint.

Parameters from the server's own tool schema.

RISK

Why sap_update_agent is rated Medium

Modifies agent configuration and metadata reversibly; requires local signing; high blast radius if AI misuses to alter pricing or capabilities.

From the tool's definition update the connected wallet SAP agent using SDK AgentModule.update; refresh name, description, capabilities, pricing, supported protocols, x402 endpoint, or metadataUri.

Risk signalsHigh parameter count (25 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_update_agent Rate-limited

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

FAQ

Questions about sap_update_agent

What does the sap_update_agent tool do? +

Local-signer-only: update the connected wallet SAP agent using SDK AgentModule.update. Hosted accountless SAP MCP rejects this direct write before x402 payment; hosted users should call sap_payments_update_agent from the local sap_payments bridge. SAP MCP context: Use this after sap_register_agent to refresh name, description, capabilities, pricing, supported protocols, x402 endpoint, or metadataUri. For NFT-backed identity changes, update the Metaplex asset first when needed, then point the SAP agent metadataUri at the current metadata document. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use sap_payments_update_agent 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 sap_update_agent accept? +

sap_update_agent accepts 9 parameters: name, agentId, pricing, agentUri, protocols, description, metadataUri, 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_update_agent? +

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

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

Can I rate-limit sap_update_agent? +

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

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

sap_update_agent 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

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 →