Attach a local file to a Rocket.Chat room or thread. Provide the
AI agents use upload_file to create or update resources in Rocket Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rocket Cli environment.
This tool creates new data (file attachments) in Rocket.Chat, which is a reversible write operation. It does not execute code, delete data, or move money. Severity is medium because unauthorized file uploads could introduce malware, phishing content, or sensitive information leakage to chat participants, but the impact is scoped to the target room/thread rather than system-wide.
From the tool's definition Tool name 'upload_file' and description 'Attach a local file to Rocket.Chat room or thread' indicate file attachment creation in a remote system.
Attacks that exploit this kind of access
Attach a local file to a Rocket.Chat room or thread. Provide the. It is categorised as a Write tool in the Rocket Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rocket Cli MCP server in PolicyLayer and add a rule for upload_file: 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 Rocket Cli. Nothing to install.
upload_file 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_file 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_file. 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_file is provided by the Rocket Cli MCP server (jeanfbrito/rocket-cli). 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 →