Retrieve the full content of a specific Jamf documentation article. This tool fetches and parses a Jamf documentation article, converting it to a clean, readable format. Works with any article from docs.jamf.com or learn.jamf.com. Args: - url (string, required): Full URL of the article (must be f...
AI agents call jamf_docs_get_article 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 |
|---|---|---|---|
url | string | — | Full URL of the Jamf documentation article. Alternative: use mapId + contentId for direct fetch. |
mapId | string | — | Fluid Topics map ID (from search results or TOC). Use with contentId for direct fetch. |
section | string | — | Extract only a specific section by title or ID (e.g., "Prerequisites", "Configuration") |
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 |
contentId | string | — | Fluid Topics content ID (from search results or TOC). Use with mapId for direct fetch. |
maxTokens | integer | — | Maximum tokens in response (100-50000, default: 5000) |
outputMode | string | — | Output detail level: "full" for detailed output or "compact" for brief output |
summaryOnly | boolean | — | Return only article summary and outline instead of full content (token-efficient) |
includeRelated | boolean | — | Include related article links in the response |
responseFormat | string | — | Output format: "markdown" for human-readable or "json" for machine-readable |
Parameters from the server's own tool schema.
This tool only retrieves and displays existing documentation content with no ability to modify, delete, or execute operations. It is a pure read operation accessing public documentation resources. The optional parameters allow filtering what is returned but do not change the underlying data. Severity is low because misuse would only expose publicly available documentation.
From the tool's definition Tool description states it "Retrieve[s] the full content" and "fetches and parses" documentation articles. Arguments include optional filtering (section, summaryOnly) but no modification capabilities.
Risk signalsAccepts URL/endpoint input (url) · High parameter count (10 properties)
Attacks that exploit this kind of access
Retrieve the full content of a specific Jamf documentation article. This tool fetches and parses a Jamf documentation article, converting it to a clean, readable format. Works with any article from docs.jamf.com or learn.jamf.com. Args: - url (string, required): Full URL of the article (must be from docs.jamf.com or learn.jamf.com) - section (string, optional): Extract only a specific section by title or ID (e.g., "Prerequisites", "Configuration") - summaryOnly (boolean, optional): Return only article summary and outline instead of full content (default: false). Token-efficient way to preview an article - includeRelated (boolean, optional): Include links to related articles (default: false) - maxTokens (number, optional): Maximum tokens in response 100-50000 (default: 5000) - outputMode ('full' | 'compact'): Output detail level (default: 'full'). Use 'compact' for brief output - responseFormat ('markdown' | 'json'): Output format (default: 'markdown') Returns: For JSON format: { "title": string, "content": string, "url": string, "product": string, "version": string, "breadcrumb": string[], "relatedArticles": [...], "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number }, "sections": [ { "id": string, "title": string, "level": number, "tokenCount": number } ] } For Markdown format: The article content with token info and available sections. Examples: - Get full article: url="https://learn.jamf.com/en-US/bundle/jamf-pro-documentation/page/Configuration_Profiles.html" - Get specific section: url="...", section="Prerequisites" - Limit response size: url="...", maxTokens=2000 Errors: - "Article not found (404)" if the URL returns a 404 error - "Invalid URL" if the URL is not from docs.jamf.com or learn.jamf.com - "Section not found" if the specified section doesn't exist (will list available sections) Note: Large articles are intelligently truncated with remaining sections listed. Use the section parameter to retrieve specific sections for long articles. It is categorised as a Read tool in the Jamf Docs MCP Server, which means it retrieves data without modifying state.
jamf_docs_get_article accepts 10 parameters: url, mapId, section, language, contentId, maxTokens, outputMode, summaryOnly, includeRelated, responseFormat. 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_article: 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_article 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_article 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_article. 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_article 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 →