// SCAN REPORT

Tickr

71 tools. 46 can modify or destroy data without limits.

11 destructive tools with no built-in limits. Policy required.

Last updated:

46 can modify or destroy data
25 read-only
71 tools total

Verified server · catalogue entry verified 05/07/2026 · full schemas captured for 66 of 71 tools

How to control Tickr ↓

TOOL MAP

What Tickr exposes to your agents

Read (25) Write / Execute (35) Destructive / Financial (11)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Tickr costs in tokens

7,617 tokens of tool definitions, loaded on every request
3.8% of a 200k context window
245 heaviest tool: update_ticket

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS
Critical Risk

The most dangerous Tickr tools

Destructive · High delete_attachment Deletion of attachments cannot be undone and permanently removes content from a ticket. Destructive · High delete_comment This tool permanently removes a comment, which cannot be undone. Destructive · High delete_cycle This tool performs an irreversible deletion operation that cannot be undone. Destructive · High delete_epic Deleting an epic from a project management system removes the epic and likely its associated metadata irreversibly.

46 of Tickr's 71 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Tickr

PolicyLayer is an MCP gateway — it sits between your AI agents and Tickr, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete_attachment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add_comment": {
    "limits": [
      {
        "counter": "add_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "generate_release_notes": {
    "limits": [
      {
        "counter": "generate_release_notes_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Tickr — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON TICKR →

Instant setup, no code required.

FULL CATALOGUE

All 71 Tickr tools

DESTRUCTIVE 11 tools
Destructive delete_attachment Delete an attachment from a ticket Destructive delete_comment Delete a comment Destructive delete_cycle Delete a cycle (sprint) from a project Destructive delete_epic Delete an epic from a project Destructive delete_implementation_item Delete an implementation item from a ticket Destructive delete_label Delete a label from a project Destructive delete_status Delete a workflow status from a project Destructive delete_ticket Delete a ticket by display number Destructive remove_epic_dependency Remove a dependency between two epics Destructive remove_project_member Remove a member from a project Destructive remove_relation Remove a relation from a ticket by relation ID
WRITE 35 tools
Write add_comment Add a comment to a ticket Write add_epic_dependency Add a dependency between two epics (predecessor blocks successor) Write add_label Add a label to a ticket Write add_project_member Add a member to a project with a specific role Write add_relation Create a relation between two tickets (blocks, relates_to, duplicates) Write add_release_ticket Link a ticket to a release Write apply_preset Apply a workflow preset to a project (replaces current statuses and transitions) Write assign_cycle Assign a ticket to a cycle (sprint) Write assign_epic Assign a ticket to an epic Write complete_dev_task Mark a dev agent task as completed with summary, branch name, and commit hash Write create_cycle Create a new cycle (sprint) in a project Write create_epic Create a new epic in a project Write create_implementation_item Add a new implementation item to a ticket Write create_label Create a new label in a project Write create_project Create a new project Write create_release Create a new release in a project Write create_status Create a new workflow status in a project Write create_ticket Create a new ticket in a project Write fail_dev_task Mark a dev agent task as failed with a reason Write link_commit Link a git commit to a ticket Write publish_release Publish a draft release — sets status to published and records publishedAt timestamp Write remove_label Remove a label from a ticket Write remove_release_ticket Remove a ticket from a release Write triage_accept Accept tickets from triage inbox — move them to a target status Write triage_reject Reject tickets from triage inbox — move them to cancelled Write update_comment Update the text of an existing comment Write update_cycle Update a cycle (sprint) in a project Write update_epic Update an epic in a project Write update_implementation_item Update an implementation item on a ticket Write update_label Update a label in a project Write update_project_member_role Update the role of a project member Write update_release Update a release (name, notes, status) Write update_status Update a workflow status in a project Write update_ticket Update ticket fields (status, title, content, priority, assignee, scope) Write update_transitions Replace all workflow transitions for a project
READ 25 tools
Read generate_release_notes Generate markdown release notes from linked tickets (client-side generation) Read get_board Get kanban board view for a project (tickets grouped by status columns) Read get_my_tasks Get tickets assigned to the current user across all projects Read get_next_statuses Get available next statuses for a ticket (based on current status and user role) Read get_project Get project detail by slug Read get_release Get full release detail including linked tickets Read get_ticket Get full ticket detail by display number Read list_attachments List attachments on a ticket Read list_comments List comments on a ticket Read list_cycles List cycles (sprints) for a project Read list_dev_assignments List all dev queue assignments (pending, in-progress, completed, failed) Read list_epics List epics for a project Read list_labels List labels for a project Read list_project_members List members of a project with their roles Read list_projects List all projects accessible to the current user Read list_relations List all relations for a ticket Read list_releases List releases in a project with optional status filter Read list_statuses List workflow statuses for a project Read list_tickets List tickets with optional filters Read list_transitions List workflow transitions for a project Read list_workflow_presets List all available workflow presets Read poll_dev_queue Poll for next dev task in the agent queue. Returns ticket details and assigned skills/instructions. Use projec Read search_tickets Fulltext search in ticket titles and content Read triage_list List tickets in triage inbox for a project Read whoami Get current user/agent identity — display name, role, tenant, token name
EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Yaver 1060 tools
admin
Nodebench 824 tools
admin
UnClick 813 tools
admin
Binance MCP Server 734 tools
admin
Pfsense 680 tools
admin
AdButler 622 tools
admin
Fortimanager 584 tools
admin
Crow 573 tools
admin
FAQ

Questions about Tickr

Can an AI agent delete data through the Tickr MCP server? +

Yes. The Tickr server exposes 11 destructive tools including delete_attachment, delete_comment, delete_cycle. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Tickr? +

The Tickr server has 35 write tools including add_comment, add_epic_dependency, add_label. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Tickr.

How many tools does the Tickr MCP server expose? +

71 tools across 3 categories: Destructive, Read, Write. 25 are read-only. 46 can modify, create, or delete data.

How do I enforce a policy on Tickr? +

Register the Tickr MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Tickr tool call.

Deterministic rules across all 71 Tickr tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TICKR →

Instant setup, no code required.

71 Tickr tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.