# get_signed_url

获取COS对象的临时签名URL

Agent View of the PolicyLayer registry record for `get_signed_url`. HTML page: https://policylayer.com/tools/156554395-tx-cos-mcp/get-signed-url

## Facts

- Tool: `get_signed_url`
- 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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why get_signed_url is rated Low

Generating signed URLs is a read operation—it retrieves authentication tokens to access data without modifying or deleting anything. The 'temporary' nature limits exposure window. While signed URLs can theoretically be misused to grant unintended access, the tool itself performs only credential generation, making it Read category with low severity since it has no direct side effects on data integrity or availability.

From the tool's own definition: "Tool name 'get_signed_url' and description '获取COS对象的临时签名URL' (Get temporary signed URL for COS object) indicate generation of read-only access URLs. This is a non-destructive operation that generates temporary credentials for accessing existing objects."

## Use case

AI agents call get_signed_url to retrieve information from Tencent Cloud COS MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. 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": {
    "get_signed_url": {}
  }
}
```

## 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_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_file` — Write — https://policylayer.com/tools/156554395-tx-cos-mcp/upload-file.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