sap_premium_webhook_relay_status
Returns the status of buffer-only (relay) webhook subscriptions for a session, including the relay configuration, buffered event count, and per-subscription delivery stats. Use this to check how many events are waiting in the server-side buffer before calling sap_premium_stream_poll or sap_premiu...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-premium-webhook-relay-status.md
What sap_premium_webhook_relay_status does on Sap
AI agents call sap_premium_webhook_relay_status to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sessionId | string | Yes | Premium session id to inspect relay subscriptions and buffered event counts for. |
Parameters from the server's own tool schema.
Why sap_premium_webhook_relay_status is rated Low
Queries webhook subscription status and buffer metrics without modifying data or triggering actions.
From the tool's definition Returns status of webhook subscriptions, relay configuration, buffered event count, delivery stats.
Attacks that exploit this kind of access
The rule that runs sap_premium_webhook_relay_status 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_relay_status, this is the rule to start with:
sap_premium_webhook_relay_status is read-only, so it stays allowed. 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_premium_webhook_relay_status call is checked against it from then on.
Questions about sap_premium_webhook_relay_status
Returns the status of buffer-only (relay) webhook subscriptions for a session, including the relay configuration, buffered event count, and per-subscription delivery stats. Use this to check how many events are waiting in the server-side buffer before calling sap_premium_stream_poll or sap_premium_stream_flush to consume them. SAP MCP execution guidance: Intent: SAP MCP tool workflow. 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 Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_premium_webhook_relay_status accepts 1 parameter: sessionId. Required: sessionId. 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_premium_webhook_relay_status: 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_premium_webhook_relay_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sap_premium_webhook_relay_status 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_premium_webhook_relay_status. 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_premium_webhook_relay_status 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