Low Risk

get_docs_chapter

get_docs_chapter

How to control get_docs_chapter ↓

What get_docs_chapter does on Typst MCP Server

AI agents call get_docs_chapter 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.

Low Risk

Why get_docs_chapter needs a policy

This tool retrieves documentation content from the Typst system with no apparent side effects. The 'get' prefix and context of sibling documentation-listing tools confirm this is a read operation. Confidence is moderate (0.7) because the description is empty, requiring reliance on naming conventions and sibling context.

From the tool's definition Tool name 'get_docs_chapter' with 'get' prefix and sibling tools like 'list_docs_chapters' and 'get_docs_chapters' indicate retrieval of documentation data. Description is empty, but the naming pattern confirms read-only data access.

Documented attack patterns abuse exactly the kind of access get_docs_chapter gives an agent:

How to control get_docs_chapter

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 get_docs_chapter:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_docs_chapter": {}
  }
}

get_docs_chapter is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Typst MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_docs_chapter

What does the get_docs_chapter tool do? +

get_docs_chapter. It is categorised as a Read tool in the Typst MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_docs_chapter? +

Register the Typst MCP Server MCP server in PolicyLayer and add a rule for get_docs_chapter: 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.

What risk level is get_docs_chapter? +

get_docs_chapter is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_docs_chapter? +

Yes. Add a rate_limit block to the get_docs_chapter 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.

How do I block get_docs_chapter completely? +

Set action: deny in the PolicyLayer policy for get_docs_chapter. 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.

What MCP server provides get_docs_chapter? +

get_docs_chapter 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.

Enforce policy on every Typst MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.