sap_skills_self_update
Refresh local agent skill files from the latest published @oobe-protocol-labs/sap-mcp-server package. Local-mode only (hosted MCP cannot write to the caller machine). Requires confirm: true. Uses npm pack + tar extraction; no shell interpolation of paths. SAP MCP execution guidance: Intent: agent...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-skills-self-update.md
What sap_skills_self_update does on Sap
AI agents use sap_skills_self_update 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 |
|---|---|---|---|
agent | string | — | Agent parameter for Self-Update SAP MCP Skills. |
skills | array | — | Skills parameter for Self-Update SAP MCP Skills. |
confirm | boolean | — | Confirm flag required before local signing, payment, or write execution. Set true only after the user approves the preview/cost. |
targetDir | string | — | Target Dir parameter for Self-Update SAP MCP Skills. |
Parameters from the server's own tool schema.
Why sap_skills_self_update is rated Medium
Modifies local files irreversibly via package extraction; requires explicit confirmation but remains reversible.
From the tool's definition Refresh local agent skill files, npm pack + tar extraction, write to caller machine
Attacks that exploit this kind of access
The rule that runs sap_skills_self_update 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_skills_self_update, this is the rule to start with:
sap_skills_self_update 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_skills_self_update call is checked against it from then on.
Questions about sap_skills_self_update
Refresh local agent skill files from the latest published @oobe-protocol-labs/sap-mcp-server package. Local-mode only (hosted MCP cannot write to the caller machine). Requires confirm: true. Uses npm pack + tar extraction; no shell interpolation of paths. SAP MCP execution guidance: Intent: agent bootstrap, routing, skills, or repair guidance. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. 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.
sap_skills_self_update accepts 4 parameters: agent, skills, confirm, targetDir. 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_skills_self_update: 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_skills_self_update 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_skills_self_update 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_skills_self_update. 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_skills_self_update 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