sap_agent_identity_plan
Free read-only planner for SAP agent registration, profile/image updates, Metaplex/MPL Core identity linking, SNS linking, x402 pricing metadata, and post-write verification. Use this before sap_payments_register_agent or sap_payments_update_agent so agents know the exact local-signer route, meta...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-agent-identity-plan.md
What sap_agent_identity_plan does on Sap
AI agents use sap_agent_identity_plan 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 | — | Required public display name for the SAP agent. Keep it stable enough for explorers and humans. |
agentId | string | — | Optional stable lowercase agent id, for example solking. This is separate from the on-chain agent PDA. |
pricing | array | — | Optional pricing tiers advertised by the agent. Use tokenType usdc + settlementMode x402 for pay.sh/x402 agent commerce. |
agentUri | string | — | Optional public HTTPS/IPFS/Arweave/Kommodo URI for the agent profile metadata or profile page. Never use local desktop file paths. |
imageUrl | string | — | Optional public image URL. This must be HTTPS, IPFS, Arweave, or another public URI; desktop file paths are not valid. |
protocols | array | — | Required protocol tags the agent supports, for example sap, mcp, jupiter, pyth, metaplex, sns, x402, payments. |
snsDomain | string | — | Optional .sol domain to link after ownership or registration is verified. |
description | string | — | Required public description of what the agent does, which protocols it can use, and its safety/trust boundaries. |
metadataUri | string | — | Alias for agentUri. Prefer a public JSON metadata document containing name, description, image, external_url, attributes, sap, metaplex, sns, and x402 fields. |
ownerWallet | string | — | Optional expected SAP owner wallet. Use this for verification planning only; signing still comes from the active local SAP profile. |
capabilities | array | — | Required capability list. Prefer object form for production; strings are accepted as shorthand. |
x402Endpoint | string | — | Optional public x402 discovery/payment endpoint, usually https://host/.well-known/x402 for external agent services. |
Parameters from the server's own tool schema.
Why sap_agent_identity_plan is rated Medium
An AI agent can call sap_agent_identity_plan faster than any human can review: one bad instruction and it creates or modifies resources in Sap by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (30 properties)
Attacks that exploit this kind of access
The rule that runs sap_agent_identity_plan 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_agent_identity_plan, this is the rule to start with:
sap_agent_identity_plan 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_agent_identity_plan call is checked against it from then on.
Questions about sap_agent_identity_plan
Free read-only planner for SAP agent registration, profile/image updates, Metaplex/MPL Core identity linking, SNS linking, x402 pricing metadata, and post-write verification. Use this before sap_payments_register_agent or sap_payments_update_agent so agents know the exact local-signer route, metadata contract, forbidden actions, and protocol fee verification checklist. It does not touch chain and never signs. 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: agent bootstrap, routing, skills, or repair guidance. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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.
sap_agent_identity_plan accepts 12 parameters: name, agentId, pricing, agentUri, imageUrl, protocols, snsDomain, description, metadataUri, ownerWallet, capabilities, x402Endpoint. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_agent_identity_plan: 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.
sap_agent_identity_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sap_agent_identity_plan 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.
Set action: deny in the PolicyLayer policy for sap_agent_identity_plan. 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.
sap_agent_identity_plan 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.
More on Sap, and thousands of servers like it.
This server
Across the catalogue