AI agents use upload_document 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.
Uploading a document is a reversible write operation that creates new content or adds files to the repository. It is not destructive (not irreversible), not financial, and not arbitrary code execution. While the tool modifies the state of the Alfresco repository, the operation can be undone by deleting the uploaded document.
From the tool's definition Tool name is 'upload_document' and description states 'Upload a document to Alfresco.' This action creates or modifies data in the content management system by adding new documents.
Documented attack patterns abuse exactly the kind of access upload_document 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 upload_document:
{
"version": "1",
"default": "deny",
"tools": {
"upload_document": {
"limits": [
{
"counter": "upload_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} upload_document 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.
Upload a document to Alfresco. 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 upload_document: 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.
upload_document 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 upload_document 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 upload_document. 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.
upload_document 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.