update_ticket_status · Vidal Helpdesk MCP: Risk & Policy

WHAT IT DOES

What update_ticket_status does on Vidal Helpdesk

AI agents use update_ticket_status to create or update resources in Vidal Helpdesk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vidal Helpdesk environment.

WHY IT NEEDS A POLICY

Why update_ticket_status needs a policy

This tool creates or modifies data (ticket status and timestamps) but does not irreversibly delete records or execute arbitrary code. The state changes are reversible—a ticket's status can be changed from 'closed' back to 'open' or 'in_progress'.

From the tool's definition Tool description states it 'Update[s] ticket status' and 'Auto-sets resolved_at/closed_at', which are reversible modifications to existing ticket records in the helpdesk system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_ticket_status Rate-limited

update_ticket_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_ticket_status": {
      "limits": [
        {
          "counter": "update_ticket_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vidal Helpdesk, so you can run agents against it safely.

FAQ

Questions about update_ticket_status

What does the update_ticket_status tool do? +

Update ticket status: open/in_progress/pending_customer/pending_third_party/resolved/closed. Optional internal comment. Auto-sets resolved_at/closed_at. It is categorised as a Write tool in the Vidal Helpdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_ticket_status? +

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

What risk level is update_ticket_status? +

update_ticket_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_ticket_status? +

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

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

update_ticket_status is provided by the Vidal Helpdesk MCP server (vidal-renao/vidal-helpdesk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.