respond_to_ticket · Tickiti MCP: Risk & Policy

WHAT IT DOES

What respond_to_ticket does on Tickiti

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

WHY IT NEEDS A POLICY

Why respond_to_ticket needs a policy

This tool creates or appends data to an existing ticket reversibly. Responses can be edited or deleted later, making it a Write operation rather than Destructive. The impact is medium severity because an agent could spam tickets, add misleading responses, or expose sensitive information via internal notes if misused, but the changes are not irreversible and do not result in data loss or financial harm.

From the tool's definition Tool description states 'Add a response to an existing ticket', which creates new data (a response/comment) attached to a ticket record. The ability to set is_internal=true indicates it modifies ticket state and metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

respond_to_ticket Rate-limited

respond_to_ticket 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": {
    "respond_to_ticket": {
      "limits": [
        {
          "counter": "respond_to_ticket_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 Tickiti, so you can run agents against it safely.

FAQ

Questions about respond_to_ticket

What does the respond_to_ticket tool do? +

Add a response to an existing ticket. Set is_internal=true for a staff-only note. It is categorised as a Write tool in the Tickiti MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on respond_to_ticket? +

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

What risk level is respond_to_ticket? +

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

Can I rate-limit respond_to_ticket? +

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

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

respond_to_ticket is provided by the Tickiti MCP server (tickiti/tickiti-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.