Retrieve multiple Jamf documentation articles in a single request. Fetches up to 10 articles in parallel with concurrency control. Useful for comparing articles, gathering information from multiple pages, or bulk research. Args: - urls (string[], required): Array of 1-10 article URLs (must be fro...
AI agents call jamf_docs_batch_get_articles 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 |
|---|---|---|---|
urls | array | Yes | Array of Jamf documentation article URLs (1-10) |
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 | — | Total token budget across all articles (100-50000, default: 5000) |
outputMode | string | — | Output detail level: "full" for detailed output or "compact" for brief output |
concurrency | integer | — | Maximum parallel requests (1-5, default: 3) |
responseFormat | string | — | Output format: "markdown" for human-readable or "json" for machine-readable |
Parameters from the server's own tool schema.
This is a batch documentation retrieval tool with no side effects. It queries and retrieves data from Jamf's public documentation without creating, modifying, deleting, or executing anything. The concurrency and token budget parameters are purely read-side optimizations. Classification as Read is appropriate with low severity given the limited blast radius of misuse (redundant documentation retrieval).
From the tool's definition Tool description states it 'Retrieve[s] multiple Jamf documentation articles' and 'Fetches up to 10 articles in parallel'. The functionality is purely informational retrieval from documentation pages with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Retrieve multiple Jamf documentation articles in a single request. Fetches up to 10 articles in parallel with concurrency control. Useful for comparing articles, gathering information from multiple pages, or bulk research. Args: - urls (string[], required): Array of 1-10 article URLs (must be from docs.jamf.com or learn.jamf.com) - concurrency (number, optional): Max parallel requests 1-5 (default: 3) - maxTokens (number, optional): Total token budget across all articles (default: 5000). Distributed evenly. - outputMode ('full' | 'compact'): Output detail level (default: 'full'). Use 'compact' for brief output. - responseFormat ('markdown' | 'json'): Output format (default: 'markdown') Returns: An array of article results. Each article independently succeeds or fails. For JSON format, returns a BatchResponse object with results, summary, and tokenInfo. Examples: - Compare two products: urls=["https://learn.jamf.com/.../page/A.html", "https://learn.jamf.com/.../page/B.html"] - Bulk fetch with compact output: urls=[...], outputMode="compact", maxTokens=10000 Note: Token budget is split evenly across articles. Use higher maxTokens for more articles. Partial failures are reported per-article without failing the entire batch. It is categorised as a Read tool in the Jamf Docs MCP Server, which means it retrieves data without modifying state.
jamf_docs_batch_get_articles accepts 6 parameters: urls, language, maxTokens, outputMode, concurrency, responseFormat. Required: urls. 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_batch_get_articles: 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_batch_get_articles 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_batch_get_articles 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_batch_get_articles. 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_batch_get_articles 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 →