search_tickets

Search Zendesk tickets

SERVERNcp SOURCE@portel/ncp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/search-tickets.md

WHAT IT DOES

What search_tickets does on Ncp

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

RISK

Why search_tickets is rated Low

Searching is a read-only operation that retrieves information from Zendesk without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—an agent could retrieve sensitive ticket information, but cannot alter or delete data, making this a low-severity read operation.

From the tool's definition Tool name 'search_tickets' and description 'Search Zendesk tickets' indicate a query operation that retrieves ticket data without modifying it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_tickets safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_tickets, this is the rule to start with:

search_tickets Allowed

search_tickets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_tickets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every search_tickets call is checked against it from then on.

FAQ

Questions about search_tickets

What does the search_tickets tool do? +

Search Zendesk tickets. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_tickets? +

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

What risk level is search_tickets? +

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

Can I rate-limit search_tickets? +

Yes. Add a rate_limit block to the search_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 search_tickets completely? +

Set action: deny in the PolicyLayer policy for search_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 search_tickets? +

search_tickets is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →