sap_premium_plugin_template
Free premium plugin manifest builder. Generates a strict, data-only stream/webhook/tool manifest template that teams can place in a private plugin subrepo, validate, plug, and unplug without executing untrusted code or exposing provider secrets. SAP MCP execution guidance: Intent: SAP MCP tool wo...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-premium-plugin-template.md
What sap_premium_plugin_template does on Sap
AI agents call sap_premium_plugin_template 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 |
|---|---|---|---|
title | string | — | Human-readable plugin and capability title shown to agent runtimes. |
pluginId | string | Yes | Lowercase premium plugin id, for example sap-premium-custom-alpha. This becomes the manifest id. |
publisher | string | — | Publisher name used for enterprise review and marketplace metadata. |
visibility | string | — | Discovery visibility. Use private or enterprise for non-public provider contracts. |
description | string | — | Full agent-facing description explaining the use case, provider boundary, pricing model, and what the capability delivers. |
providerEnv | array | — | Uppercase provider env var names required to make the capability live. Do not pass secret values. |
capabilityId | string | Yes | Lowercase capability id, for example custom.signal.stream or custom:tool:score. |
unitPriceUsd | number | — | Suggested x402/pay.sh unit price in USD. Agents should see pricing before activation. |
capabilityType | string | Yes | Capability type to template: stream, webhook, or tool. |
Parameters from the server's own tool schema.
Why sap_premium_plugin_template is rated Low
Even though sap_premium_plugin_template only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs sap_premium_plugin_template 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_plugin_template, this is the rule to start with:
sap_premium_plugin_template 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_plugin_template call is checked against it from then on.
Questions about sap_premium_plugin_template
Free premium plugin manifest builder. Generates a strict, data-only stream/webhook/tool manifest template that teams can place in a private plugin subrepo, validate, plug, and unplug without executing untrusted code or exposing provider secrets. 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_plugin_template accepts 9 parameters: title, pluginId, publisher, visibility, description, providerEnv, capabilityId, unitPriceUsd, capabilityType. Required: pluginId, capabilityId, capabilityType. 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_plugin_template: 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_plugin_template 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_plugin_template 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_plugin_template. 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_plugin_template 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