tiktok.user_reposts
List reposts for a TikTok user. Provide either user_id or unique_id, not both. Pass cursor from a previous response to fetch the next page. Cost = 3 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/tiktok.user-reposts.md
What tiktok.user_reposts does on Vee3
AI agents call tiktok.user_reposts to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | object | — | Number of items to return (max 30). |
cursor | object | — | Pagination cursor from a previous response. |
user_id | object | — | TikTok numeric user id. |
unique_id | object | — | TikTok unique id (username). |
Parameters from the server's own tool schema.
Why tiktok.user_reposts is rated Low
This tool retrieves and queries publicly available repost data from TikTok without side effects. It performs a read operation on existing data, matching the Read category definition of 'retrieves or queries data; no side effects (search, list, get, fetch)'. The low cost and straightforward list-and-paginate functionality pose minimal risk if misused by an agent.
From the tool's definition Tool description states 'List reposts for a TikTok user' with pagination support via cursor. The verb 'List' and the retrieval-only nature (fetching existing public data from TikTok) indicates no modifications, deletions, or code execution.
Attacks that exploit this kind of access
The rule that runs tiktok.user_reposts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tiktok.user_reposts, this is the rule to start with:
tiktok.user_reposts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every tiktok.user_reposts call is checked against it from then on.
Questions about tiktok.user_reposts
List reposts for a TikTok user. Provide either user_id or unique_id, not both. Pass cursor from a previous response to fetch the next page. Cost = 3 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
tiktok.user_reposts accepts 4 parameters: count, cursor, user_id, unique_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for tiktok.user_reposts: 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 Vee3. Nothing to install.
tiktok.user_reposts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tiktok.user_reposts 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 tiktok.user_reposts. 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.
tiktok.user_reposts is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue