Get complete TikTok creator profile including metadata, follower stats, hashtags, niches, and content analysis.
AI agents call tiktok_get_profile to retrieve information from CreatorDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available creator profile information from TikTok via the CreatorDB API. It performs no writes, modifications, deletive operations, code execution, or financial transactions.
From the tool's definition Tool name 'tiktok_get_profile' and description 'Get complete TikTok creator profile including metadata, follower stats, hashtags, niches, and content analysis' indicate data retrieval only.
Attacks that exploit this kind of access
Get complete TikTok creator profile including metadata, follower stats, hashtags, niches, and content analysis. It is categorised as a Read tool in the CreatorDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CreatorDB MCP Server MCP server in PolicyLayer and add a rule for tiktok_get_profile: 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 CreatorDB MCP Server. Nothing to install.
tiktok_get_profile 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_get_profile 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_get_profile. 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_get_profile is provided by the CreatorDB MCP Server MCP server (saiyamvora13/creatordb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →