create_ticket_task · Freshservice MCP Server MCP

WHAT IT DOES

What create_ticket_task does on Freshservice MCP Server

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

WHY IT NEEDS A POLICY

Why create_ticket_task needs a policy

The tool creates (writes) a new task record, which is a reversible operation—tasks can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The severity is medium because while task creation is a side effect, it affects service desk workflow and ticket tracking but has a contained blast radius within a single ticket.

From the tool's definition Tool name 'create_ticket_task' and description 'Create a new task on a Freshservice ticket' explicitly indicate data creation. This is a reversible write operation that adds a new task record to an existing ticket.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_ticket_task Rate-limited

create_ticket_task 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": {
    "create_ticket_task": {
      "limits": [
        {
          "counter": "create_ticket_task_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 Freshservice MCP Server, so you can run agents against it safely.

FAQ

Questions about create_ticket_task

What does the create_ticket_task tool do? +

Create a new task on a Freshservice ticket. It is categorised as a Write tool in the Freshservice MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_ticket_task? +

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

What risk level is create_ticket_task? +

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

Can I rate-limit create_ticket_task? +

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

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

create_ticket_task is provided by the Freshservice MCP Server MCP server (tannertm0/freshservice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.