tiktok.video_details
Look up metadata for a TikTok video. Provide either video_id or video_url, not both. Cost = 1 token.
This record as markdown: /tools/io-github-vee3io-vee3/tiktok.video-details.md
What tiktok.video_details does on Vee3
AI agents call tiktok.video_details 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 |
|---|---|---|---|
video_id | object | — | TikTok video id. |
video_url | object | — | TikTok video URL. |
Parameters from the server's own tool schema.
Why tiktok.video_details is rated Low
The tool performs a query operation that retrieves publicly available metadata from TikTok without creating, modifying, deleting, executing code, or moving money. It has minimal blast radius—worst case is that an agent retrieves metadata it shouldn't, but no side effects occur. The low cost (1 token) and straightforward read-only nature further support this classification.
From the tool's definition Tool description states 'Look up metadata for a TikTok video' using video_id or video_url. This is a retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs tiktok.video_details 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.video_details, this is the rule to start with:
tiktok.video_details 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.video_details call is checked against it from then on.
Questions about tiktok.video_details
Look up metadata for a TikTok video. Provide either video_id or video_url, not both. Cost = 1 token. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
tiktok.video_details accepts 2 parameters: video_id, video_url. 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.video_details: 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.video_details 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.video_details 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.video_details. 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.video_details 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