Secure ServiceNow AI Agents
Catch It Before It Reaches Anyone.
Built for Now Assist and Otto, ServiceNow's CSM AI agents
Inspect every message your ServiceNow AI agent sends and receives, even the ones that look harmless. Catch sensitive data and manipulated prompts before either gets through.Inspect every message your ServiceNow AI agent sends and receives, even the ones that look harmless.
ServiceNow Now Assist / Otto · SOC 2 Type II · AICPA
Metomic inspects both directions of the conversation, over the same connection your CSM AI agent already uses.
One API-based integration, both directions
Metomic connects to ServiceNow CSM through Inbound Email Actions and the custom chat integration framework, an integration point that carries a customer's message in and your AI agent's reply back out.
An API integration, not an agent change
Metomic connects at Inbound Email Actions for the email channel and the custom chat integration framework for Virtual Agent/chat — real, documented points where ServiceNow already exposes the conversation.
- No agent-side install, no proxy, no network change
- Uses ServiceNow's own documented integration points
- Fits alongside the security tools you already run
Reads what the customer sends in
Metomic checks what's actually inside the message for sensitive data and for attempts to manipulate the agent. A customer typing a card number into a case, or trying to talk your AI agent into ignoring its own instructions, gets caught before the agent ever sees it.
- Checks the whole message, not just where it came from
- Catches attempts to manipulate the agent, not only sensitive data
- Uses the same policy your security team already trusts elsewhere
Decides, in the moment, on either side
Metomic allows the message through, cleans it up first, or holds it for a person to look at, whichever fits, whether it's heading into your AI agent or back out to the customer.
- Allow, clean up, or hold, not just a blunt block
- Same engine, same decisions, both directions
- Your policy decides what happens if something's unclear
Checks what your AI agent sends back, too
Before a reply reaches the customer, Metomic checks it the same way: nothing sensitive goes out that shouldn't, over the same email or chat connection.
- Catches a reply that would repeat back sensitive data
- Same connection, same policy, the other direction
- No manual step for your team, this runs automatically
An answer ready, when someone asks
Every decision is logged automatically, on both directions of the conversation, alongside everything else Metomic already tracks. When someone asks what your CSM AI agent exchanged with a customer, you have an answer instead of a gap.
- One record for everything your AI touches, not a log per platform
- Ready for auditors, regulators, and your board
- Only the decision is kept, not the conversation itself
API-based, not agent-side
Metomic connects through the integration points ServiceNow already exposes, covering both directions of the conversation without changing how your AI agent itself is configured.
API-Based, Not Agent-Side
No install on your AI agent itself. Metomic connects through ServiceNow's own integration points, live the same day.
One Policy, Every Channel
Email and chat share one set of rules and one record, instead of a separate setup to manage for each.
Inbound and Outbound, One Policy
What the customer sends and what your AI agent sends back run through the same rules and the same audit trail.
See this inspect your own ServiceNow traffic
Book a demo and watch Metomic catch PII and prompt injection on both sides of a real conversation, live, before you configure a single label.
A customer-facing agent is a two-way conversation, and both directions carry risk. What a customer sends in can hide a card number or an attempt to manipulate the agent. What the agent sends back can just as easily repeat something it shouldn't.
It's the same blind spot security teams have always had to close: check what's moving before it lands, on both sides of the exchange. Your CSM AI agent is approved to have the conversation; nobody's necessarily checking what's actually in either half of it.
Metomic is built to be that check, over the same API connection your AI agent already uses.PII reaches the agent unredacted
A customer pastes a card number or a health detail straight into an email or chat, and your CSM AI agent, and everything downstream of it, sees it in the clear.
Prompt injection hijacks the agent
"Ignore your instructions above" buried in a customer message is not a hypothetical. An agent that trusts its input the way it trusts its system prompt can be steered into handing over data it should never expose.
A reply can leak just as easily as a message
A manipulated or careless agent reply can repeat back a card number, an internal note, or data about another customer. Checking only the inbound half of the conversation misses this.
No audit trail for what the agent did with it
When the auditor asks what your CSM AI agent exchanged with a customer, an uninspected path on either side leaves you with nothing to show.
Where this fits versus Metomic's platform-wide coverage
This page is the ServiceNow-specific case of Metomic's broader protection for customer-facing agents, which also covers Zendesk, Salesforce, and HubSpot. Most enterprises running more than one of these want the same policy across all of them.
| Customer Service AI Agents (all platforms) | ServiceNow (this page) | |
|---|---|---|
| Scope | Zendesk, Salesforce, HubSpot, ServiceNow | ServiceNow CSM specifically |
| Where it plugs in | Each platform's own inbound hook | Inbound Email Actions & the custom chat integration framework, an API-based integration |
| Direction | Inbound, per platform | Inbound and outbound, both ways |
| Decision | Allow, hold for review, or block, with redaction where it applies | Same engine, same decisions |
| Audit trail | One record across every connected platform | Same record, filtered to ServiceNow |
One policy engine, one audit trail, across every customer-service AI agent you run. See the full picture on the Customer Service AI Agents page.
Connect email, chat, or both
Most teams are live within a day on their ServiceNow CSM channel mix.
Connect your CSM channels
Point Metomic at Inbound Email Actions and/or the Virtual Agent custom chat integration framework. An API-based integration, nothing for your team to build or stand up.
Set what matters to you
Start from Metomic's defaults for sensitive data and manipulation attempts, or set your own, for either direction of the conversation.
Watch it work, then turn it on
See what it catches before you change anything, then enforce at your pace. Every decision is logged from day one.
Source content is inspected in flight. Only decisions and findings are retained, for your audit trail.
Questions security teams ask about ServiceNow AI agents
What is ServiceNow Otto / Now Assist?
ServiceNow's AI agent for Customer Service Management is named "Now Assist for CSM" in its still-published prior-release documentation and "ServiceNow Otto for Customer Service Management" in its newest release documentation — both names are currently live across ServiceNow's own docs.
How does Metomic connect to ServiceNow CSM?
Through an API-based integration, at the points ServiceNow already documents: Inbound Email Actions for the email channel, and the custom chat integration framework for Virtual Agent/chat. There's nothing to install on the agent itself.
Does this cover what your AI agent sends back, not just what it receives?
Yes. Metomic inspects both directions over the same connection: the customer message coming in, and the reply going back out, before either one lands.
Which ServiceNow CSM channels does this cover?
Email and Virtual Agent (chat), through ServiceNow's own Inbound Email Actions and custom chat integration framework. Talk to us about your specific deployment to confirm coverage for your channel mix.
How is this different from Shadow AI discovery?
Shadow AI discovery finds AI tools your own employees are using without approval. This is the opposite direction: it inspects messages arriving from and sent to people outside your organization, your customers, around a sanctioned, approved agent. Both matter; they cover different traffic.
How is this different from the MCP Gateway or Inference Hooks?
The MCP Gateway and Inference Hooks govern what an internal agent or employee sends to a model. This governs your CSM AI agent's conversation with customers directly: what comes in from them, and what the agent sends back. Both run through the same Metomic policy engine and the same audit trail.
Give your ServiceNow AI agent a decision it can trust, both ways
Book a demo and watch Metomic inspect real inbound and outbound traffic bound for your own ServiceNow CSM deployment, live, before you configure a single label.