# upload_file

上传单个文件到腾讯云COS

Agent View of the PolicyLayer registry record for `upload_file`. HTML page: https://policylayer.com/tools/156554395-tx-cos-mcp/upload-file

## Facts

- Tool: `upload_file`
- Server: Tencent Cloud COS MCP Server (`156554395/tx-cos-mcp`) — https://policylayer.com/tools/156554395-tx-cos-mcp.md
- Homepage: https://github.com/156554395/tx-cos-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "upload_file",
    "arguments": {}
  }
}
```

## Why upload_file is rated Medium

The tool creates or modifies data in cloud object storage by uploading files. This is a Write operation with high severity because unintended uploads could store malicious, sensitive, or corrupted files in production cloud storage, affecting availability and data integrity for applications relying on that storage.

From the tool's own definition: "Tool name 'upload_file' and description '上传单个文件到腾讯云COS' (upload a single file to Tencent Cloud COS) directly indicate file creation/modification in cloud storage."

## Use case

AI agents use upload_file to create or update resources in Tencent Cloud COS MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tencent Cloud COS MCP Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Tencent Cloud COS MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_file": {
      "limits": [
        {
          "counter": "upload_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Tencent Cloud COS MCP Server (16)

- `clear_upload_progress` — Destructive — https://policylayer.com/tools/156554395-tx-cos-mcp/clear-upload-progress.md
- `delete_folder` — Destructive — https://policylayer.com/tools/156554395-tx-cos-mcp/delete-folder.md
- `delete_multiple` — Destructive — https://policylayer.com/tools/156554395-tx-cos-mcp/delete-multiple.md
- `delete_object` — Destructive — https://policylayer.com/tools/156554395-tx-cos-mcp/delete-object.md
- `manage_temp_files` — Destructive — https://policylayer.com/tools/156554395-tx-cos-mcp/manage-temp-files.md
- `get_folder_stats` — Read — https://policylayer.com/tools/156554395-tx-cos-mcp/get-folder-stats.md
- `get_signed_url` — Read — https://policylayer.com/tools/156554395-tx-cos-mcp/get-signed-url.md
- `get_upload_progress` — Read — https://policylayer.com/tools/156554395-tx-cos-mcp/get-upload-progress.md
- `list_folders` — Read — https://policylayer.com/tools/156554395-tx-cos-mcp/list-folders.md
- `list_objects` — Read — https://policylayer.com/tools/156554395-tx-cos-mcp/list-objects.md
- `copy_object` — Write — https://policylayer.com/tools/156554395-tx-cos-mcp/copy-object.md
- `create_folder` — Write — https://policylayer.com/tools/156554395-tx-cos-mcp/create-folder.md
- `move_object` — Write — https://policylayer.com/tools/156554395-tx-cos-mcp/move-object.md
- `rename_object` — Write — https://policylayer.com/tools/156554395-tx-cos-mcp/rename-object.md
- `upload_large_file` — Write — https://policylayer.com/tools/156554395-tx-cos-mcp/upload-large-file.md
- `upload_multiple` — Write — https://policylayer.com/tools/156554395-tx-cos-mcp/upload-multiple.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=156554395-tx-cos-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/156554395-tx-cos-mcp
