sap_premium_webhook_register

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

Medium RISK CLASS

Category Write

Parameters 43 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-premium-webhook-register.md

WHAT IT DOES

What sap_premium_webhook_register does on Sap

AI agents use sap_premium_webhook_register 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
`events`	array	Yes	Exact event ids to deliver, from the capability delivery contract.
`sessionId`	string	Yes	Active premium session id.
`targetUrl`	string	Yes	HTTPS webhook endpoint owned by the buyer. Localhost and private network URLs are rejected in production.
`signingPublicKey`	string	—	Optional buyer public key for webhook signature verification.

Parameters from the server's own tool schema.

RISK

Why sap_premium_webhook_register is rated Medium

Webhook registration modifies system state by configuring persistent event routing and delivery endpoints, constituting a write operation with potential security implications if misconfigured.

From the tool's definition Registers HTTPS webhook target for premium event delivery; signed events

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_premium_webhook_register Rate-limited

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

FAQ

Questions about sap_premium_webhook_register

What does the sap_premium_webhook_register tool do? +

Registers an HTTPS webhook target for signed premium event delivery. The session must be active (activated via sap_premium_activate_session). The target URL must be HTTPS, reachable, and not a private/localhost endpoint in production. Events are filtered to the exact event ids listed in the request. SAP MCP execution guidance: Intent: local-signer write workflow. 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.

What parameters does sap_premium_webhook_register accept? +

sap_premium_webhook_register accepts 4 parameters: events, sessionId, targetUrl, signingPublicKey. Required: events, sessionId, targetUrl. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_premium_webhook_register? +

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

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

Can I rate-limit sap_premium_webhook_register? +

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

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

sap_premium_webhook_register 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

team_manager_register_agents on Team Manager MCP → The MCP Attack Database →

Guides

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