comms_render_message

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 93 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/comms-render-message.md

WHAT IT DOES

What comms_render_message does on Servicialo

AI agents use comms_render_message to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.

Parameter	Type	Required
`data`	object	Yes
`width`	number	—
`action`	string	—
`apiKey`	string	—
`orgSlug`	string	Yes
`clientId`	string	—
`template`	string	Yes
`whatsappTo`	string	—
`whatsappBody`	string	—

Parameters from the server's own tool schema.

RISK

Why comms_render_message is rated Medium

The tool modifies external state by sending messages through WhatsApp, which is a reversible write operation. While sending communication is less severe than financial transactions or destructive operations, it creates persistent artifacts (rendered messages, WhatsApp delivery) and could be misused to spam or impersonate users.

From the tool's definition Tool description states it can "render and send via WhatsApp with the image attached" using the "send" action. This creates and transmits communication artifacts (PNG images + WhatsApp messages) on behalf of the user.

Risk signalsHandles credentials or secrets (apiKey) · Accepts raw HTML/template content (template)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comms_render_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comms_render_message, this is the rule to start with:

comms_render_message Rate-limited

comms_render_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "comms_render_message": {
      "limits": [
        {
          "counter": "comms_render_message_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 Servicialo, apply this rule, and every comms_render_message call is checked against it from then on.

FAQ

Questions about comms_render_message

What does the comms_render_message tool do? +

Render a communication template as a visual image (PNG). Available templates: session-confirmation, session-reminder, payment-reminder. Use action "preview" to get the image URL, "send" to render and send via WhatsApp with the image attached. Each template requires specific data fields (clientName, providerName, date, time, etc.). It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does comms_render_message accept? +

comms_render_message accepts 9 parameters: data, width, action, apiKey, orgSlug, clientId, template, whatsappTo, whatsappBody. Required: data, orgSlug, template. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on comms_render_message? +

Register the Servicialo MCP server in PolicyLayer and add a rule for comms_render_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 Servicialo. Nothing to install.

What risk level is comms_render_message? +

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

Can I rate-limit comms_render_message? +

Yes. Add a rate_limit block to the comms_render_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.

How do I block comms_render_message completely? +

Set action: deny in the PolicyLayer policy for comms_render_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.

What MCP server provides comms_render_message? +

comms_render_message is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools →

Across the catalogue

The MCP Attack Database →

Guides

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