422 without launching. The workflow receives the reviewed
department label as companyName; the signed request body and HMAC contract remain unchanged.Platform operators manage bindings through the customers MCP group with
getFreshserviceDepartmentBinding and putFreshserviceDepartmentBinding, backed by GET and
PUT /api/v2/customers/freshservice-department-bindings. Changes use revision CAS and are audited.
External Apps are refused; use a platform or Personal API key. Activation also requires a forge-mcp
release containing the refreshed bundled operation catalog.PUT writes retain the existing confirmation or preauthorization requirements. Deploy the backend
with PUT confirmation support before activating the refreshed MCP catalog.RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset on every response of every operation. Until now they were left off every 401, a route’s own 429 and the shared 503, but those statuses carry them whenever the request spent from its bucket first:- an operation’s own
401, such as an External App’s user token that fails; - the general bucket’s
429on an operation that also has a tighter limit of its own; - a
503after the spend, such as a transient fault while the operation ran.
401 from authentication, a stopped api_keys door’s 503 governance_door_stopped), a route’s own 429 and the limiter’s own 503 still carry none; the header descriptions say so. See rate limiting.
