Get metadata and properties of a document or folder.
AI agents call get_node_properties to retrieve information from Alfresco MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata/properties from existing nodes in the repository. It is a read-only operation with no side effects, no data modification, no code execution, and no destructive capabilities. The blast radius of misuse is minimal—an agent could only access information that already exists in the repository. This clearly fits the 'Read' category, which encompasses query and fetch operations.
From the tool's definition Tool name 'get_node_properties' and description 'Get metadata and properties of a document or folder' indicate retrieval of existing data without modification, creation, deletion, or execution of operations.
Documented attack patterns abuse exactly the kind of access get_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 get_node_properties:
{
"version": "1",
"default": "deny",
"tools": {
"get_node_properties": {}
}
} get_node_properties is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get metadata and properties of a document or folder. It is categorised as a Read tool in the Alfresco MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Alfresco MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_node_properties 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_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 get_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.
get_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.