get-document-type-allowed-at-root
Get document types that are allowed at root level
This record as markdown: /tools/mcp-dev/get-document-type-allowed-at-root.md
What get-document-type-allowed-at-root does on Mcp Dev
AI agents call get-document-type-allowed-at-root 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.
Why get-document-type-allowed-at-root is rated Low
This tool retrieves configuration metadata about which document types are permitted at the root level of an Umbraco CMS hierarchy. It has no side effects, does not modify data, execute code, or perform destructive operations. It is a simple informational lookup.
From the tool's definition Tool name 'get-document-type-allowed-at-root' and description 'Get document types that are allowed at root level' indicate a retrieval operation. The verb 'get' and lack of any modification, deletion, or execution semantics confirm this is a query-only action.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs get-document-type-allowed-at-root safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-document-type-allowed-at-root, this is the rule to start with:
get-document-type-allowed-at-root is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every get-document-type-allowed-at-root call is checked against it from then on.
Questions about get-document-type-allowed-at-root
Get document types that are allowed at root level. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-document-type-allowed-at-root: 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 Mcp Dev. Nothing to install.
get-document-type-allowed-at-root 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 get-document-type-allowed-at-root 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 get-document-type-allowed-at-root. 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.
get-document-type-allowed-at-root is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue