tiktok.search_users
Search TikTok users by keyword. Requires query. Pass cursor from a previous response to fetch the next page. Cost = 5 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/tiktok.search-users.md
What tiktok.search_users does on Vee3
AI agents call tiktok.search_users 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). |
query | string | Yes | Search keywords. |
cursor | object | — | Pagination cursor from a previous response. |
follower_count | object | — | Follower count filter: 0-4. |
Parameters from the server's own tool schema.
Why tiktok.search_users is rated Low
This tool queries and returns TikTok user data in response to a keyword search. It retrieves information without side effects, creating no irreversible changes, code execution, or financial impact. Pagination via cursor is a standard read-only pattern. Classification: Read (lowest severity category).
From the tool's definition 'Search TikTok users by keyword' — performs a retrieval operation with pagination support. No modification, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
The rule that runs tiktok.search_users 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.search_users, this is the rule to start with:
tiktok.search_users 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.search_users call is checked against it from then on.
Questions about tiktok.search_users
Search TikTok users by keyword. Requires query. Pass cursor from a previous response to fetch the next page. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
tiktok.search_users accepts 4 parameters: count, query, cursor, follower_count. Required: query. 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.search_users: 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.search_users 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.search_users 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.search_users. 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.search_users 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