// SCAN REPORT

Zd

8 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 28 Jun 2026

4 can modify or destroy data

4 read-only

8 tools total

Community server · catalogue entry verified 28/06/2026

How to control Zd ↓

TOOL MAP

What Zd exposes to your agents

Read (4) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Zd tools

Write · Medium zendesk_add_private_note Add a private internal note to a Zendesk ticket Write · Medium zendesk_add_public_note Add a public comment to a Zendesk ticket Write · Medium zendesk_create_ticket Create a new Zendesk ticket Write · Medium zendesk_update_ticket Update a Zendesk ticket

4 of Zd's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Zd

PolicyLayer is an MCP gateway — it sits between your AI agents and Zd, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "zendesk_add_private_note": {
    "limits": [
      {
        "counter": "zendesk_add_private_note_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "zendesk_get_linked_incidents": {
    "limits": [
      {
        "counter": "zendesk_get_linked_incidents_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Zd — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ZD →

Instant setup, no code required.

FULL CATALOGUE

All 8 Zd tools

WRITE 4 tools

Write zendesk_add_private_note Add a private internal note to a Zendesk ticket Write zendesk_add_public_note Add a public comment to a Zendesk ticket Write zendesk_create_ticket Create a new Zendesk ticket Write zendesk_update_ticket Update a Zendesk ticket

READ 4 tools

Read zendesk_get_linked_incidents Fetch all incident tickets linked to a particular ticket Read zendesk_get_ticket Get a Zendesk ticket by ID Read zendesk_get_ticket_details Get detailed information about a Zendesk ticket including comments Read zendesk_search Search for Zendesk tickets based on a query

FAQ

Questions about Zd

How do I prevent bulk modifications through Zd? +

The Zd server has 4 write tools including zendesk_add_private_note, zendesk_add_public_note, zendesk_create_ticket. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Zd.

How many tools does the Zd MCP server expose? +

8 tools across 2 categories: Read, Write. 4 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Zd? +

Register the Zd MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Zd tool call.

Deterministic rules across all 8 Zd tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ZD →

Instant setup, no code required.

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