Low Risk

list_request_tickets

Lists request tickets (sc_request) with optional filters.

How to control list_request_tickets ↓

What list_request_tickets does on Snow

AI agents call list_request_tickets to retrieve information from Snow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_request_tickets needs a policy

The tool retrieves and lists existing request tickets from ServiceNow's service catalog (sc_request table) with optional filtering. It performs data retrieval only, with no capability to create, modify, delete, or execute operations. This is a standard read-only query operation with minimal security risk, hence low severity.

From the tool's definition Tool name 'list_request_tickets' and description 'Lists request tickets (sc_request) with optional filters' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access list_request_tickets gives an agent:

How to control list_request_tickets

PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for list_request_tickets:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_request_tickets": {}
  }
}

list_request_tickets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Snow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_request_tickets

What does the list_request_tickets tool do? +

Lists request tickets (sc_request) with optional filters. It is categorised as a Read tool in the Snow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_request_tickets? +

Register the Snow MCP server in PolicyLayer and add a rule for list_request_tickets: 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 Snow. Nothing to install.

What risk level is list_request_tickets? +

list_request_tickets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_request_tickets? +

Yes. Add a rate_limit block to the list_request_tickets 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.

How do I block list_request_tickets completely? +

Set action: deny in the PolicyLayer policy for list_request_tickets. 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.

What MCP server provides list_request_tickets? +

list_request_tickets is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Snow tool call.

Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.