move_ticket · Pearlog MCP: Risk & Policy

WHAT IT DOES

What move_ticket does on Pearlog

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

PARAMETERS

Parameter	Type	Required	Description
`id`	number	Yes	Ticket ID to move.
`projectId`	number	Yes	Destination project ID.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why move_ticket needs a policy

This tool modifies ticket state by relocating it across projects, which is a reversible change. It does not delete data (would be Destructive) or execute arbitrary code (would be Execute). The medium severity reflects that misuse could disrupt project organization and ticket tracking, but the change is reversible via moving the ticket back.

From the tool's definition Tool name 'move_ticket' and description 'Move a ticket to a different project' indicate modification of ticket metadata/state by changing its project association.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_ticket Rate-limited

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

FAQ

Questions about move_ticket

What does the move_ticket tool do? +

Move a ticket to a different project. It is categorised as a Write tool in the Pearlog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does move_ticket accept? +

move_ticket accepts 2 parameters: id, projectId. Required: id, projectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on move_ticket? +

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

What risk level is move_ticket? +

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

Can I rate-limit move_ticket? +

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

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

move_ticket is provided by the Pearlog MCP server (mcp-server-pearlog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.