New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

snow_inbound_email_action

Manage inbound email actions: list, get, create, update, delete, enable/disable

SERVERSerac SOURCEserac-labs/serac
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/serac/snow-inbound-email-action.md

What snow_inbound_email_action does on Serac

AI agents call snow_inbound_email_action to permanently remove resources in Serac, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why snow_inbound_email_action is rated Critical

The tool explicitly includes 'delete' as one of its operations, which is irreversible. It also spans Read (list, get), Write (create, update, enable/disable), and Destructive (delete) categories. Per the rules, the most severe applicable category is Destructive. Misuse could permanently remove inbound email action configurations in ServiceNow, disrupting automated email processing workflows.

From the tool's definition Manage inbound email actions: list, get, create, update, delete, enable/disable

Questions about snow_inbound_email_action

What does the snow_inbound_email_action tool do? +

Manage inbound email actions: list, get, create, update, delete, enable/disable. It is categorised as a Destructive tool in the Serac MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on snow_inbound_email_action? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_inbound_email_action: 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.

What risk level is snow_inbound_email_action? +

snow_inbound_email_action is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit snow_inbound_email_action? +

Yes. Add a rate_limit block to the snow_inbound_email_action 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 snow_inbound_email_action completely? +

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

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

More on Serac, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Serac's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.