upload_company_document
AI agents use upload_company_document to create or update resources in MCP Multi-Agent Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Multi-Agent Server environment.
Upload operations are Write category—they create or persist data. Severity is high because uploading documents to a company system could introduce malicious content, overwrite legitimate files, or compromise data integrity if an agent uploads without proper validation.
From the tool's definition Tool name is 'upload_company_document' which directly indicates creation/modification of company documents. Description is empty, limiting specificity, but the name unambiguously indicates a write operation that adds data to a company system.
Attacks that exploit this kind of access
upload_company_document. It is categorised as a Write tool in the MCP Multi-Agent Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Multi-Agent Server MCP server in PolicyLayer and add a rule for upload_company_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 MCP Multi-Agent Server. Nothing to install.
upload_company_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_company_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_company_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_company_document is provided by the MCP Multi-Agent Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent-public). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →