// SCAN REPORT

Vidal Helpdesk

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

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

Last updated: 30 Jun 2026

4 can modify or destroy data

3 read-only

7 tools total

Community server · catalogue entry verified 30/06/2026

How to control Vidal Helpdesk ↓

TOOL MAP

What Vidal Helpdesk exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Vidal Helpdesk tools

Write · Medium prioritize_incident The tool modifies existing ticket data by updating priority and upserting AI analysis fields. Write · Medium create_ticket This tool creates new records in a persistent database (Supabase), which is a write operation that modifies system state. Write · Medium suggest_solution This tool creates new comment records and modifies ticket status, making it a Write operation. Write · Medium update_ticket_status This tool creates or modifies data (ticket status and timestamps) but does not irreversibly delete records or execute arbitrary code.

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

POLICY

How to control Vidal Helpdesk

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

Rate limit write operations

{
  "create_ticket": {
    "limits": [
      {
        "counter": "create_ticket_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "generate_report": {
    "limits": [
      {
        "counter": "generate_report_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 Vidal Helpdesk — 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 VIDAL HELPDESK →

Instant setup, no code required.

FULL CATALOGUE

All 7 Vidal Helpdesk tools

WRITE 4 tools

Write create_ticket Create an IT support ticket with full AI triage (Claude Sonnet). Priority: low/medium/high/critical. Saves to Write prioritize_incident Re-run AI triage on an existing ticket with optional new context. Updates priority and upserts ai_analysis if Write suggest_solution Generate step-by-step IT solution in DE/EN/ES/FR/IT. Saves as internal comment in ticket_comments. Updates sta Write update_ticket_status Update ticket status: open/in_progress/pending_customer/pending_third_party/resolved/closed. Optional internal

READ 3 tools

Read generate_report Generate real helpdesk report from Supabase for today/week/month. SLA compliance, priority breakdown, avg reso Read get_ticket_status Get full details of a ticket by ref (e.g. Read list_tickets List tickets with optional filters by status and priority. Returns up to 50 tickets with AI summary.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Vidal Helpdesk

How do I prevent bulk modifications through Vidal Helpdesk? +

The Vidal Helpdesk server has 4 write tools including create_ticket, prioritize_incident, suggest_solution. 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 Vidal Helpdesk.

How many tools does the Vidal Helpdesk MCP server expose? +

7 tools across 3 categories: Execute, Read, Write. 3 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Vidal Helpdesk? +

Register the Vidal Helpdesk 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 Vidal Helpdesk tool call.

Deterministic rules across all 7 Vidal Helpdesk tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON VIDAL HELPDESK →

Instant setup, no code required.

7 Vidal Helpdesk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.