publish-document-with-descendants
Publishes a document and its descendants by Id. This is an asynchronous operation that may take time for large document trees. The tool will poll for completion and return the final result when finished.
This record as markdown: /tools/mcp-dev/publish-document-with-descendants.md
What publish-document-with-descendants does on Mcp Dev
AI agents use publish-document-with-descendants to create or update resources in Mcp Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.
Why publish-document-with-descendants is rated Medium
Publishing documents is a reversible write operation that changes content state and visibility. While potentially impactful (affecting multiple descendants), it is not destructive (data remains intact and can be unpublished), not financial, and not execute (no arbitrary code execution).
From the tool's definition Tool name 'publish-document-with-descendants' and description states it 'Publishes a document and its descendants' — this modifies the published state of content in Umbraco CMS, affecting multiple documents and potentially public-facing content visibility.
Attacks that exploit this kind of access
The rule that runs publish-document-with-descendants 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 publish-document-with-descendants, this is the rule to start with:
publish-document-with-descendants stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 publish-document-with-descendants call is checked against it from then on.
Questions about publish-document-with-descendants
Publishes a document and its descendants by Id. This is an asynchronous operation that may take time for large document trees. The tool will poll for completion and return the final result when finished. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for publish-document-with-descendants: 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.
publish-document-with-descendants is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the publish-document-with-descendants 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 publish-document-with-descendants. 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.
publish-document-with-descendants 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