Unified tool for the ServiceNow Key Management Framework. Covers KMF modules (sys_kmf_module), cryptographic modules (sys_kmf_crypto_module), and keys (sys_kmf_key) for use in PII/PCI encryption flows and Edge Encryption. Actions: - list_modules — list KMF modules (sys_kmf_module) and their crypt...
AI agents use snow_kms_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.
While the tool includes read operations (list_modules, list_keys) and cryptographic operations (encrypt, decrypt), the presence of create_key and rotate_key that write to sys_kmf_key tables makes this fundamentally a Write category tool. The writes are reversible (new keys can be rotated out, old versions retained).
From the tool's definition Tool description states "create a new key under a KMF module (writes sys_kmf_key)" and "rotate_key — generate a new active version". Actions include create_key, rotate_key which modify KMF state.
Attacks that exploit this kind of access
Unified tool for the ServiceNow Key Management Framework. Covers KMF modules (sys_kmf_module), cryptographic modules (sys_kmf_crypto_module), and keys (sys_kmf_key) for use in PII/PCI encryption flows and Edge Encryption. Actions: - list_modules — list KMF modules (sys_kmf_module) and their crypto modules - create_key — create a new key under a KMF module (writes sys_kmf_key) - encrypt — encrypt a plaintext payload using the named key - decrypt — decrypt a ciphertext payload using the named key - list_keys — list keys, optionally filtered by module - rotate_key — generate a new active version of a key and deactivate the previous one Use when: managing KMF modules and keys for sensitive data, rotating keys on schedule, or wrapping/unwrapping payloads through the platform. Encrypt and decrypt invoke a server-side helper Script Include rather than the Table API; falls back to a scripted-execution path if the dedicated endpoint is absent. Returns: action-specific data. List operations return arrays of KMF records (sys_id, name, module, type, active, key_format). Create/rotate return the new key record. Encrypt/decrypt return the wrapped/unwrapped payload as a string. Plaintext and ciphertext are never logged in error metadata. 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_kms_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_kms_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_kms_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_kms_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_kms_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_kms_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 →