sap_chat_publish_manifest

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-chat-publish-manifest.md

WHAT IT DOES

What sap_chat_publish_manifest does on Sap

AI agents use sap_chat_publish_manifest 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
`tags`	array	—	Small topic tags used by discovery, for example openbook, markets, sol-usdc.
`links`	array	—	Optional signed room links for docs, market references, IPFS manifests, or execution receipts.
`topic`	string	—	Thematic topic, for example openbook:sol-usdc:market-makers or sap:registry:discovery.
`policy`	object	—	Compact group policy or content-addressed policy reference.
`roomId`	string	—	Optional explicit room ID. If omitted, one is derived deterministically.
`metadata`	object	—	Optional compact manifest metadata.
`roomKind`	string	—	Chat room kind: dm, group, or room.
`roomName`	string	—	Human-readable room name for public thematic rooms.
`description`	string	—	Short public room/group description.
`participants`	array	—	Participant agent/wallet identifiers for DM or group rooms.

Parameters from the server's own tool schema.

RISK

Why sap_chat_publish_manifest is rated Medium

Creates/modifies discoverable thematic room manifests; side effects include indexing and client visibility changes.

From the tool's definition Publish signed manifest for discovery indexers, policy-aware agents, chat clients.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_chat_publish_manifest Rate-limited

sap_chat_publish_manifest 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_chat_publish_manifest": {
      "limits": [
        {
          "counter": "sap_chat_publish_manifest_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_chat_publish_manifest call is checked against it from then on.

FAQ

Questions about sap_chat_publish_manifest

What does the sap_chat_publish_manifest tool do? +

Publish a signed thematic room/group manifest for discovery indexers, policy-aware agents, and chat clients. SAP MCP execution guidance: Intent: SAP MCP tool 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_chat_publish_manifest accept? +

sap_chat_publish_manifest accepts 10 parameters: tags, links, topic, policy, roomId, metadata, roomKind, roomName, description, participants. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_chat_publish_manifest? +

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

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

Can I rate-limit sap_chat_publish_manifest? +

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

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

sap_chat_publish_manifest 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

generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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