Look up a term in the Jamf official glossary and get its definition. This tool searches glossary pages across Jamf product documentation and returns matching term definitions using fuzzy matching. Note: Glossary content is currently only available in English (en-US). Non-English language paramete...
AI agents call jamf_docs_glossary_lookup 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 |
|---|---|---|---|
term | string | Yes | Glossary term to look up (e.g., "MDM", "Configuration Profile", "Smart Group") |
product | string | — | Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect |
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 lookup tool that retrieves definition data from documentation. It has no side effects, does not modify data, execute code, delete content, or involve financial transactions. The fuzzy matching search capability does not change its classification as a Read operation—it is still fundamentally a data retrieval mechanism with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Look up a term in the Jamf official glossary and get its definition' and 'searches glossary pages across Jamf product documentation and returns matching term definitions'.
Attacks that exploit this kind of access
Look up a term in the Jamf official glossary and get its definition. This tool searches glossary pages across Jamf product documentation and returns matching term definitions using fuzzy matching. Note: Glossary content is currently only available in English (en-US). Non-English language parameters are accepted but results will be in English. Args: - term (string, required): Glossary term to look up (2-100 characters). Supports fuzzy matching. - product (string, optional): Filter by product ID (use jamf_docs_list_products to see all) - language (string, optional): Documentation language/locale (default: en-US). Note: glossary is English-only. - maxTokens (number, optional): Maximum tokens in response 100-50000 (default: 5000) - outputMode ('full' | 'compact'): Output detail level (default: 'full') - responseFormat ('markdown' | 'json'): Output format (default: 'markdown') Returns: For JSON format: { "term": string, "totalMatches": number, "entries": [{ "term": string, "definition": string, "product": string, "url": string }], "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number } } For Markdown format: A formatted list of glossary definitions with source links. Examples: - "What is MDM?" → term="MDM" - "Configuration Profile in Jamf Pro" → term="Configuration Profile", product="jamf-pro" - "What does DEP stand for?" → term="DEP" Errors: - "No matching term found" if no glossary entries match - "Invalid product ID" if product parameter is not recognized. It is categorised as a Read tool in the Jamf Docs MCP Server, which means it retrieves data without modifying state.
jamf_docs_glossary_lookup accepts 6 parameters: term, product, language, maxTokens, outputMode, responseFormat. Required: term. 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_glossary_lookup: 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_glossary_lookup 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_glossary_lookup 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_glossary_lookup. 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_glossary_lookup 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 →