Lists all chapters in the typst docs. The LLM should use this in the beginning to get the list of chapters and then decide which chapter to read.
AI agents call list_docs_chapters to retrieve information from Typst MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns a list of documentation chapters. It performs no modifications, deletions, code execution, or other side effects. It is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Lists all chapters in the typst docs' - a pure retrieval operation with no side effects. The instruction to use this 'to get the list of chapters and then decide which chapter to read' confirms it is informational only.
Documented attack patterns abuse exactly the kind of access list_docs_chapters gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Typst MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_docs_chapters:
{
"version": "1",
"default": "deny",
"tools": {
"list_docs_chapters": {}
}
}list_docs_chapters is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all chapters in the typst docs. The LLM should use this in the beginning to get the list of chapters and then decide which chapter to read. It is categorised as a Read tool in the Typst MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Typst MCP Server MCP server in PolicyLayer and add a rule for list_docs_chapters: 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 Typst MCP Server. Nothing to install.
list_docs_chapters is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_docs_chapters 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 list_docs_chapters. 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.
list_docs_chapters is provided by the Typst MCP Server MCP server (johannesbrandenburger/typst-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Typst MCP Server, 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.
8 Typst MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.