Get the table of contents for a Jamf product's documentation. This tool retrieves the navigation structure for a specific Jamf product, allowing you to browse available documentation topics. Args: - product (string, required): Product ID - one of: jamf-pro, jamf-school, jamf-connect, jamf-protect...
AI agents call jamf_docs_get_toc to retrieve information from Jamf Docs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number for pagination (1-100, default: 1) |
product | string | Yes | Product ID: jamf-pro, jamf-school, jamf-connect, jamf-protect |
version | string | — | Specific version (defaults to latest) |
language | string | — | Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH |
maxTokens | integer | — | Maximum tokens in response (100-50000, default: 5000) |
outputMode | string | — | Output detail level: "full" for detailed output or "compact" for brief output |
responseFormat | string | — | Output format: "markdown" for human-readable or "json" for machine-readable |
Parameters from the server's own tool schema.
This is a straightforward read-only operation that queries and returns structured documentation metadata. The tool has no side effects—it only retrieves information from Jamf's documentation system. The optional parameters (version, page, maxTokens) control filtering and presentation but do not modify any data. This poses minimal security risk to the Jamf system or any connected infrastructure.
From the tool's definition Tool retrieves documentation table of contents with parameters like product, version, page, and maxTokens.
Attacks that exploit this kind of access
Get the table of contents for a Jamf product's documentation. This tool retrieves the navigation structure for a specific Jamf product, allowing you to browse available documentation topics. Args: - product (string, required): Product ID - one of: jamf-pro, jamf-school, jamf-connect, jamf-protect - version (string, optional): Specific version (defaults to latest) - page (number, optional): Page number for pagination 1-100 (default: 1) - maxTokens (number, optional): Maximum tokens in response 100-50000 (default: 5000) - outputMode ('full' | 'compact'): Output detail level (default: 'full'). Use 'compact' for flat list without nested children - responseFormat ('markdown' | 'json'): Output format (default: 'markdown') Returns: For JSON format: { "product": string, "version": string, "toc": [...], "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number }, "pagination": { "page": number, "pageSize": number, "totalPages": number, "totalItems": number, "hasNext": boolean, "hasPrev": boolean } } For Markdown format: A hierarchical list of documentation topics with pagination and token info. Examples: - Browse Jamf Pro documentation: product="jamf-pro" - Get page 2 of TOC: product="jamf-pro", page=2 - Limit response size: product="jamf-pro", maxTokens=2000 Errors: - "Invalid product ID" if the product is not recognized - "Version not found" if the specified version doesn't exist Note: Use this to discover what topics are available before searching or retrieving specific articles. Large TOCs are paginated. It is categorised as a Read tool in the Jamf Docs MCP Server, which means it retrieves data without modifying state.
jamf_docs_get_toc accepts 7 parameters: page, product, version, language, maxTokens, outputMode, responseFormat. Required: product. The full parameter table on this page comes from the server's own tool schema.
Register the Jamf Docs MCP server in PolicyLayer and add a rule for jamf_docs_get_toc: 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 Jamf Docs. Nothing to install.
jamf_docs_get_toc 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 jamf_docs_get_toc 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 jamf_docs_get_toc. 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.
jamf_docs_get_toc is provided by the Jamf Docs MCP server (@get-technology-inc/jamf-docs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →