create_problem
Create a new problem record (requires WRITE_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/create-problem.md
What create_problem does on ServiceNow MCP Server
AI agents use create_problem 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.
Why create_problem is rated Medium
This tool creates new records in ServiceNow, which is a reversible write operation. Data can be created and later modified or deleted. The blast radius is medium because unauthorized problem record creation could clutter the system, trigger workflows, or consume resources, but it does not irreversibly destroy data or move money.
From the tool's definition Tool name 'create_problem' combined with description 'Create a new problem record' indicates data creation. The description explicitly notes 'requires WRITE_ENABLED=true', confirming write-level permissions are needed.
Attacks that exploit this kind of access
The rule that runs create_problem safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_problem, this is the rule to start with:
create_problem stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every create_problem call is checked against it from then on.
Questions about create_problem
Create a new problem record (requires WRITE_ENABLED=true). 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 create_problem: 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.
create_problem 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 create_problem 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 create_problem. 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.
create_problem is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue