# create_sla_definition

Create SLA definitions

Agent View of the PolicyLayer registry record for `create_sla_definition`. HTML page: https://policylayer.com/tools/divyashah0510-mcp-server-servicenow/create-sla-definition

## Facts

- Tool: `create_sla_definition`
- Server: ServiceNow MCP Server (`divyashah0510/mcp-server-servicenow`) — https://policylayer.com/tools/divyashah0510-mcp-server-servicenow.md
- Homepage: https://github.com/divyashah0510/mcp-server-servicenow
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_sla_definition",
    "arguments": {}
  }
}
```

## Why create_sla_definition is rated Medium

Creating SLA definitions modifies ServiceNow configuration in a reversible manner (SLAs can be edited or deleted later). This is a Write operation rather than Execute because it creates structured data objects, not arbitrary code execution. However, severity is high because misconfigured SLAs could impact business operations, incident prioritization, and customer commitments across the organization.

From the tool's own definition: "Tool name is 'create_sla_definition' and description states 'Create SLA definitions'. This creates new Service Level Agreement objects in ServiceNow, which are configuration records that define service commitments and response/resolution time targets."

## Use case

AI agents use create_sla_definition 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches ServiceNow MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_sla_definition": {
      "limits": [
        {
          "counter": "create_sla_definition_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on ServiceNow MCP Server (6)

- `create_business_rule` — Execute — https://policylayer.com/tools/divyashah0510-mcp-server-servicenow/create-business-rule.md
- `create_client_script` — Write — https://policylayer.com/tools/divyashah0510-mcp-server-servicenow/create-client-script.md
- `create_incident` — Write — https://policylayer.com/tools/divyashah0510-mcp-server-servicenow/create-incident.md
- `create_kb_article` — Write — https://policylayer.com/tools/divyashah0510-mcp-server-servicenow/create-kb-article.md
- `create_record_producer` — Write — https://policylayer.com/tools/divyashah0510-mcp-server-servicenow/create-record-producer.md
- `create_variable_set` — Write — https://policylayer.com/tools/divyashah0510-mcp-server-servicenow/create-variable-set.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=divyashah0510-mcp-server-servicenow · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/divyashah0510-mcp-server-servicenow