update_ticket_status

Update the status of an existing support ticket.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/update-ticket-status.md

WHAT IT DOES

What update_ticket_status does on FavCRM

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

Parameter	Type	Required	Description
`status`	string	Yes	New status
`ticketId`	string	Yes	The ticket ID to update

Parameters from the server's own tool schema.

RISK

Why update_ticket_status is rated Medium

This tool updates an existing record (ticket status) reversibly. Status changes can typically be undone by updating to a different status. This is a Write operation, not Read (retrieves data), Execute (runs code), Destructive (irreversible deletion), or Financial (money movement).

From the tool's definition 'Update the status of an existing support ticket' - modifies ticket data state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_ticket_status safely

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

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.

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

FAQ

Questions about update_ticket_status

What does the update_ticket_status tool do? +

Update the status of an existing support ticket. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_ticket_status accept? +

update_ticket_status accepts 2 parameters: status, ticketId. Required: status, ticketId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_ticket_status? +

Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →