create_compliance_control
Create a Compliance Control (sn_compliance_control).
This record as markdown: /tools/tedorigawa001-servicenow-mcp/create-compliance-control.md
What create_compliance_control does on ServiceNow-MCP
AI agents use create_compliance_control to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Why create_compliance_control is rated Medium
Creating compliance controls constitutes a reversible write operation that modifies ServiceNow's compliance and audit-related data. While write operations are generally lower-risk than destructive or execute actions, compliance controls are critical infrastructure—misuse could create false compliance records, bypass audit requirements, or establish fake controls that mask actual compliance gaps.
From the tool's definition Tool name contains 'create' and description states 'Create a Compliance Control'; this operation creates new records in ServiceNow's compliance control system (sn_compliance_control table).
Attacks that exploit this kind of access
The rule that runs create_compliance_control safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_compliance_control, this is the rule to start with:
create_compliance_control 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, apply this rule, and every create_compliance_control call is checked against it from then on.
Questions about create_compliance_control
Create a Compliance Control (sn_compliance_control). It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP server in PolicyLayer and add a rule for create_compliance_control: 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. Nothing to install.
create_compliance_control 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_compliance_control 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_compliance_control. 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_compliance_control is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue