# MCP Server: Sessions & gates

> What the server enforces.

Glider documentation · Automation & API · Web page: https://cgglider.com/docs/mcp/gates/

Sections of this page: [Connecting](https://cgglider.com/docs/mcp.md) · [Tools](https://cgglider.com/docs/mcp/tools.md) · [Sessions & gates](https://cgglider.com/docs/mcp/gates.md)

- A session starts on an agent's first call for a page: a restore point is saved and the ids of everything already on the page are recorded.
- Catalog first — a tool that changes a domain refuses with catalog_required until that domain's catalog was read in the session, and every change requires the layers catalog.
- Consent — changing or deleting anything that existed before the session refuses with consent_required. The agent asks through questions; the card's wording comes from the server, and only an approval unlocks exactly those targets.
- Agent writes appear in the open editor immediately and can be undone as one step, or reverted later from the session's restore point.