17 tools from the MCP Request-tracker MCP Server, categorised by risk level.
View the MCP Request-tracker policy →Cross-Platform Works on Linux, macOS, and Windows 2/5 get_my_open_tickets Get open tickets assigned to a user 2/5 get_new_tickets Get new and unassigned tickets 2/5 get_ticket Get ticket details by ID 2/5 get_ticket_history Get ticket history and changelog 2/5 search_tickets Search tickets using RT query syntax 2/5 add_ticket_comment Add a private comment not visible to requestor 3/5 add_time_worked Add time to existing time worked 2/5 complete_weekly_checklist Complete a weekly checklist ticket with results 3/5 create_ticket Create a new ticket in Request Tracker 3/5 open_ticket Open a ticket and set it active 3/5 reply_to_ticket Add correspondence visible to the requestor 4/5 resolve_ticket Resolve and close a ticket 4/5 set_ticket_owner Set the owner of a ticket 3/5 set_ticket_status Change the status of a ticket 3/5 set_time_worked Set total time worked on a ticket 3/5 take_ticket Take ownership and open a ticket 3/5 The MCP Request-tracker MCP server exposes 17 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the MCP Request-tracker server.
MCP Request-tracker tools are categorised as Read (6), Write (11). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept