sap_publish_tool_by_name

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

Medium RISK CLASS

Category Write

Parameters 100 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-publish-tool-by-name.md

WHAT IT DOES

What sap_publish_tool_by_name does on Sap

AI agents use sap_publish_tool_by_name 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
`category`	number	—	Numeric tool category ID
`toolName`	string	—	Name of the tool to publish
`httpMethod`	number	—	HTTP method code (e.g. 0=GET, 1=POST)
`isCompound`	boolean	—	Whether the tool is a compound tool (default: false)
`protocolId`	string	—	Protocol ID the tool belongs to (e.g. "jupiter")
`description`	string	—	Human-readable description of the tool
`paramsCount`	number	—	Total number of parameters the tool accepts
`requiredParams`	number	—	Number of required parameters
`inputSchemaJson`	string	—	JSON string of the tool input schema
`outputSchemaJson`	string	—	JSON string of the tool output schema

Parameters from the server's own tool schema.

RISK

Why sap_publish_tool_by_name is rated Medium

Modifies tool registry by publishing descriptors; reversible but affects system capabilities advertised to agents.

From the tool's definition Publish tool descriptor, writes to tool registry, advertise capabilities

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_publish_tool_by_name Rate-limited

sap_publish_tool_by_name 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_publish_tool_by_name": {
      "limits": [
        {
          "counter": "sap_publish_tool_by_name_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_publish_tool_by_name call is checked against it from then on.

FAQ

Questions about sap_publish_tool_by_name

What does the sap_publish_tool_by_name tool do? +

Publish a tool descriptor using SDK ToolsModule.publishByName. SAP MCP context: Use tool registry writes to advertise concrete capabilities that this MCP can serve, including AgentKit bridge tools such as bridging_bridgeWormhole and Metaplex tools such as metaplex-nft_mintNFT. Publish only schemas and descriptions that match the actual MCP tool surface. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. 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_publish_tool_by_name accept? +

sap_publish_tool_by_name accepts 10 parameters: category, toolName, httpMethod, isCompound, protocolId, description, paramsCount, requiredParams, inputSchemaJson, outputSchemaJson. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_publish_tool_by_name? +

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

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

Can I rate-limit sap_publish_tool_by_name? +

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

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

sap_publish_tool_by_name 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

The MCP Attack Database →

Guides

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