Move a ticket to a different status and optionally reorder it
AI agents use move_ticket to create or update resources in Mcptix — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcptix environment.
This tool creates or modifies data reversibly by changing ticket status and position, fitting the Write category. It does not delete or irreversibly destroy data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely read data (not Read).
From the tool's definition The tool description states it 'Move a ticket to a different status and optionally reorder it', which modifies ticket state (status field) and potentially ordering metadata. This is a reversible change—tickets can be moved back to previous statuses.
Documented attack patterns abuse exactly the kind of access move_ticket gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcptix, and nothing reaches the server without passing your rules. This is the rule we recommend for move_ticket:
{
"version": "1",
"default": "deny",
"tools": {
"move_ticket": {
"limits": [
{
"counter": "move_ticket_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Move a ticket to a different status and optionally reorder it. It is categorised as a Write tool in the Mcptix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcptix 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 Mcptix. Nothing to install.
move_ticket is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
move_ticket is provided by the Mcptix MCP server (ownlytics/mcptix). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcptix, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Mcptix tools catalogued and risk-classified — across an index of 43,000+ MCP servers.