comms_get_preferences
Get the communication preferences for an organization (WhatsApp, email, confirmation, reminder channels and messages).
This record as markdown: /tools/com-servicialo-mcp-server/comms-get-preferences.md
What comms_get_preferences does on Servicialo
AI agents call comms_get_preferences to retrieve information from Servicialo 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 |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes |
Parameters from the server's own tool schema.
Why comms_get_preferences is rated Low
This tool retrieves organizational communication preference settings (WhatsApp, email, confirmation, reminder channels). It performs a read-only query with no capability to modify, execute, or delete data. The blast radius of misuse is minimal—an attacker gains visibility into preference metadata but cannot alter configurations, trigger actions, or access sensitive transactional data. Classified as Read/low severity.
From the tool's definition Tool name contains 'get' and description states 'Get the communication preferences' — indicates data retrieval with no modification or side effects.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs comms_get_preferences 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_get_preferences, this is the rule to start with:
comms_get_preferences 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 Servicialo, apply this rule, and every comms_get_preferences call is checked against it from then on.
Questions about comms_get_preferences
Get the communication preferences for an organization (WhatsApp, email, confirmation, reminder channels and messages). It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
comms_get_preferences accepts 2 parameters: apiKey, orgSlug. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for comms_get_preferences: 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.
comms_get_preferences 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 comms_get_preferences 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 comms_get_preferences. 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.
comms_get_preferences 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.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue