tiktok.user_following
List accounts a TikTok user follows. Requires user_id. Pass cursor from a previous response to fetch the next page. Cost = 2 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/tiktok.user-following.md
What tiktok.user_following does on Vee3
AI agents call tiktok.user_following 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 200). |
cursor | object | — | Pagination cursor from a previous response. |
user_id | string | Yes | TikTok numeric user id. |
Parameters from the server's own tool schema.
Why tiktok.user_following is rated Low
This tool performs data retrieval of a TikTok user's following list—a straightforward query operation with no ability to modify, delete, or execute code. It returns existing public relationship data. The severity is low because following lists are typically public or user-authorized information with minimal blast radius if accessed by an AI agent.
From the tool's definition Tool description states 'List accounts a TikTok user follows' with pagination via cursor, indicating a read-only query operation that retrieves and lists data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs tiktok.user_following 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_following, this is the rule to start with:
tiktok.user_following 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_following call is checked against it from then on.
Questions about tiktok.user_following
List accounts a TikTok user follows. Requires user_id. Pass cursor from a previous response to fetch the next page. Cost = 2 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
tiktok.user_following accepts 3 parameters: count, cursor, user_id. Required: user_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_following: 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_following 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_following 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_following. 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_following 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