Unified tool for ServiceNow CSM customer interactions. Wraps the interaction table (emails, chats, calls), interaction_related_record (case links), and channel-specific records reachable through them. Actions: - list — list interactions filtered by account, channel, state, or date - get — fetch a...
AI agents use snow_csm_communication_manage to create or update resources in Serac — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
The tool's primary risk stems from its ability to create new interaction records (emails, chats, calls) and link them to cases. While mostly read operations (list, get, list_for_case), the write capabilities—particularly log_interaction creating customer-facing communication records and link_to_case modifying case relationships—make this a Write category tool.
From the tool's definition Tool includes 'log_interaction — create a new interaction record' and 'link_to_case — attach an existing interaction to a CSM case', which are create and modify operations. These are reversible writes to CSM customer interaction data.
Attacks that exploit this kind of access
Unified tool for ServiceNow CSM customer interactions. Wraps the interaction table (emails, chats, calls), interaction_related_record (case links), and channel-specific records reachable through them. Actions: - list — list interactions filtered by account, channel, state, or date - get — fetch a single interaction by sys_id with linked records - log_interaction — create a new interaction record (channel, direction, body, opened_for, account, contact) - link_to_case — attach an existing interaction to a CSM case via interaction_related_record - list_for_case — list every interaction linked to a given case - list_by_channel — list interactions for a channel (email, chat, phone) within an optional date range Use when: the agent needs to log or audit customer communications around a CSM case. Companion tools: snow_create_customer_case (opens the case), snow_csm_contract_manage (defines what the customer is entitled to). For internal IT communications use the platform. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_csm_communication_manage: 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 Serac. Nothing to install.
snow_csm_communication_manage 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 snow_csm_communication_manage 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 snow_csm_communication_manage. 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.
snow_csm_communication_manage is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
snow_csm_communication_manage is one line of Serac's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →