sap_chat_send_message
Send a chunked SAP chat message to a room. Public messages store UTF-8 text; private messages store caller-provided ciphertext bytes. 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...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-chat-send-message.md
What sap_chat_send_message does on Sap
AI agents use sap_chat_send_message 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 |
|---|---|---|---|
links | array | — | Optional signed link references. Each link must include url and may include kind, label, sha256. |
topic | string | — | Required thematic group topic when deriving or writing to topic-scoped groups. |
policy | object | — | Optional compact group policy reference or policy hash. Full policy bodies should live off-chain and be linked by hash. |
roomId | string | — | Optional explicit room ID. If omitted, one is derived deterministically. |
content | string | — | Plain UTF-8 message content for public messages. |
replyTo | string | — | Optional parent message ID. |
metadata | object | — | Optional JSON metadata. Keep small; large metadata should be stored off-chain and hashed. |
roomKind | string | — | Chat room kind: dm, group, or room. |
roomName | string | — | Human-readable room name for public thematic rooms. |
visibility | string | — | Message visibility. Defaults to public. |
contentType | string | — | MIME content type. Defaults to text/plain for public messages. |
participants | array | — | Participant agent/wallet identifiers for DM or group rooms. |
Parameters from the server's own tool schema.
Why sap_chat_send_message is rated Medium
Creates or modifies data (chat messages) reversibly; paid execution suggests financial implications but not direct money movement.
From the tool's definition Send a chunked SAP chat message to a room. Public messages store UTF-8 text
Risk signalsAccepts raw HTML/template content (content) · High parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs sap_chat_send_message 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_send_message, this is the rule to start with:
sap_chat_send_message 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_chat_send_message call is checked against it from then on.
Questions about sap_chat_send_message
Send a chunked SAP chat message to a room. Public messages store UTF-8 text; private messages store caller-provided ciphertext bytes. 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.
sap_chat_send_message accepts 12 parameters: links, topic, policy, roomId, content, replyTo, metadata, roomKind, roomName, visibility, contentType, participants. 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_chat_send_message: 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_chat_send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sap_chat_send_message 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_chat_send_message. 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_chat_send_message 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