Update metadata and properties of a document or folder.
AI agents use update_node_properties to create or update resources in Alfresco MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alfresco MCP Server environment.
This tool modifies metadata and properties of existing nodes (documents/folders) in Alfresco reversibly. It does not delete data (hence not Destructive), execute arbitrary code (hence not Execute), create new nodes (primary Write, not Execute), or move money (not Financial).
From the tool's definition Tool name 'update_node_properties' and description 'Update metadata and properties of a document or folder' indicate modification of data. The word 'update' is a clear Write operation signal.
Documented attack patterns abuse exactly the kind of access update_node_properties gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Alfresco MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_node_properties:
{
"version": "1",
"default": "deny",
"tools": {
"update_node_properties": {
"limits": [
{
"counter": "update_node_properties_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_node_properties 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.
Free to start. No card required.
Update metadata and properties of a document or folder. It is categorised as a Write tool in the Alfresco MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alfresco MCP Server MCP server in PolicyLayer and add a rule for update_node_properties: 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 Alfresco MCP Server. Nothing to install.
update_node_properties 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 update_node_properties 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 update_node_properties. 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.
update_node_properties is provided by the Alfresco MCP Server MCP server (stevereiner/python-alfresco-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Alfresco MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Alfresco MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.