tiktok.music_details
Look up metadata for a TikTok music track. Provide either music_id or music_url, not both. Cost = 2 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/tiktok.music-details.md
What tiktok.music_details does on Vee3
AI agents call tiktok.music_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 |
|---|---|---|---|
music_id | object | — | TikTok music id. |
music_url | object | — | TikTok music page URL. |
Parameters from the server's own tool schema.
Why tiktok.music_details is rated Low
This is a straightforward read operation that retrieves metadata about TikTok music tracks. There are no side effects, no data modification, no code execution, and no financial implications. The tool only queries and returns information about existing music metadata. Low severity due to minimal blast radius if misused—the worst case would be excessive API calls or enumeration of music metadata.
From the tool's definition Tool description states 'Look up metadata for a TikTok music track' with parameters music_id or music_url. This is a query operation retrieving publicly available metadata with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
The rule that runs tiktok.music_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.music_details, this is the rule to start with:
tiktok.music_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.music_details call is checked against it from then on.
Questions about tiktok.music_details
Look up metadata for a TikTok music track. Provide either music_id or music_url, not both. Cost = 2 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
tiktok.music_details accepts 2 parameters: music_id, music_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.music_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.music_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.music_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.music_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.music_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