Submit a Record Producer request. Record Producers create records directly (like incidents) without using the cart. Use this for incident creation, problem reporting, and other single-record submissions from the service catalog.
AI agents use record_producer_submit to create or update resources in ServiceNow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
The tool creates or modifies records (incidents, problem reports) in ServiceNow reversibly. This is a Write operation—data is created but can be subsequently modified or deleted. Severity is medium because misuse could flood the system with spurious incident records or problem reports, creating operational noise and requiring administrative cleanup, but doesn't cause permanent destruction or financial harm.
From the tool's definition Tool description explicitly states it 'Submit[s] a Record Producer request' and 'create[s] records directly (like incidents)' via 'single-record submissions from the service catalog.' This is record creation/modification without deletion or financial impact.
Attacks that exploit this kind of access
Submit a Record Producer request. Record Producers create records directly (like incidents) without using the cart. Use this for incident creation, problem reporting, and other single-record submissions from the service catalog. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for record_producer_submit: 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 ServiceNow MCP Server. Nothing to install.
record_producer_submit 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 record_producer_submit 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 record_producer_submit. 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.
record_producer_submit is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →