zendesk_search

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

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/shriram-vasudevan-integrations-mcp/zendesk-search.md

WHAT IT DOES

What zendesk_search does on Integrations MCP

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

RISK

Why zendesk_search is rated Low

Search operations are read-only with no side effects—they retrieve and query data without modification. However, confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity.

From the tool's definition Tool name 'zendesk_search' indicates a search/query operation on Zendesk data. No description provided, but the naming convention and sibling tools (airtable_get_record, airtable_list_records, amplitude_get_event_counts) which are clearly Read operations…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zendesk_search safely

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

zendesk_search Allowed

zendesk_search 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": {
    "zendesk_search": {}
  }
}

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

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

FAQ

Questions about zendesk_search

What does the zendesk_search tool do? +

zendesk_search is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zendesk_search? +

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

What risk level is zendesk_search? +

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

Can I rate-limit zendesk_search? +

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

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

zendesk_search is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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