put-document-notifications
Updates the notifications for a document by Id.
This record as markdown: /tools/mcp-dev/put-document-notifications.md
What put-document-notifications does on Mcp Dev
AI agents use put-document-notifications 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 put-document-notifications is rated Medium
This tool modifies document notification configuration in Umbraco CMS. It is a Write operation because it updates (reversible modification of) existing data. Severity is medium because misuse could alter notification delivery for document workflows, potentially causing missed alerts or notification spam, but the changes are reversible and don't cause data loss or financial harm.
From the tool's definition Tool name 'put-document-notifications' and description 'Updates the notifications for a document by Id' indicate a modification operation that changes document notification settings.
Attacks that exploit this kind of access
The rule that runs put-document-notifications 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 put-document-notifications, this is the rule to start with:
put-document-notifications 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 put-document-notifications call is checked against it from then on.
Questions about put-document-notifications
Updates the notifications for a document by Id. 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 put-document-notifications: 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.
put-document-notifications 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 put-document-notifications 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 put-document-notifications. 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.
put-document-notifications 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