# get-document-type-ancestors-batch Gets the ancestor chain (breadcrumb) for multiple document type Ids in one call. Returns one entry per requested Id, each containing that Id Agent View of the PolicyLayer registry record for `get-document-type-ancestors-batch`. HTML page: https://policylayer.com/tools/mcp-dev/get-document-type-ancestors-batch ## Facts - Tool: `get-document-type-ancestors-batch` - Server: Mcp Dev (`@umbraco-cms/mcp-dev`) — https://policylayer.com/tools/mcp-dev.md - Install: `npx -y @umbraco-cms/mcp-dev` - Homepage: git+https://github.com/umbraco/Umbraco-CMS-MCP-Dev.git - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get-document-type-ancestors-batch", "arguments": {} } } ``` ## Why get-document-type-ancestors-batch is rated Low This tool queries hierarchical metadata about document type ancestors without modifying, executing, or deleting anything. It is a straightforward read operation on CMS metadata with minimal blast radius if misused by an AI agent. From the tool's own definition: "The tool 'gets the ancestor chain' for document types and 'returns' entries—pure retrieval with no modification, deletion, or execution. The verb 'Gets' and the read-only nature of querying a breadcrumb chain confirm it is a retrieval operation." ## Use case AI agents call get-document-type-ancestors-batch to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Dev: ```json { "version": "1", "default": "deny", "tools": { "get-document-type-ancestors-batch": {} } } ``` ## Other tools on Mcp Dev (418) - `create-document-version-rollback` — Destructive — https://policylayer.com/tools/mcp-dev/create-document-version-rollback.md - `delete-data-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-data-type.md - `delete-data-type-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-data-type-folder.md - `delete-dictionary-item` — Destructive — https://policylayer.com/tools/mcp-dev/delete-dictionary-item.md - `delete-document` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document.md - `delete-document-blueprint` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-blueprint.md - `delete-document-blueprint-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-blueprint-folder.md - `delete-document-public-access` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-public-access.md - `delete-document-recycle-bin-item` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-recycle-bin-item.md - `delete-document-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-type.md - `delete-document-type-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-type-folder.md - `delete-element` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element.md - `delete-element-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element-folder.md - `delete-element-folder-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element-folder-from-recycle-bin.md - `delete-element-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element-from-recycle-bin.md - `delete-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-from-recycle-bin.md - `delete-language` — Destructive — https://policylayer.com/tools/mcp-dev/delete-language.md - `delete-log-viewer-saved-search-by-name` — Destructive — https://policylayer.com/tools/mcp-dev/delete-log-viewer-saved-search-by-name.md - `delete-media` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media.md - `delete-media-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-from-recycle-bin.md - `delete-media-recycle-bin-item` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-recycle-bin-item.md - `delete-media-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-type.md - `delete-media-type-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-type-folder.md - `delete-member` — Destructive — https://policylayer.com/tools/mcp-dev/delete-member.md - `delete-member-group` — Destructive — https://policylayer.com/tools/mcp-dev/delete-member-group.md - `delete-member-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-member-type.md - `delete-partial-view` — Destructive — https://policylayer.com/tools/mcp-dev/delete-partial-view.md - `delete-partial-view-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-partial-view-folder.md - `delete-redirect` — Destructive — https://policylayer.com/tools/mcp-dev/delete-redirect.md - `delete-script` — Destructive — https://policylayer.com/tools/mcp-dev/delete-script.md - …and 388 more: https://policylayer.com/tools/mcp-dev.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=mcp-dev · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mcp-dev