Get historical performance data for a TikTok creator.
AI agents call tiktok_get_performance_history 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 historical analytics or metrics for a TikTok creator account. It queries and returns existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only over-retrieve data or access metrics for creators it shouldn't, but cannot modify content, delete data, or execute external actions. This is a straightforward Read operation.
From the tool's definition Tool name 'tiktok_get_performance_history' and description 'Get historical performance data for a TikTok creator' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Get historical performance data for a TikTok creator. 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_performance_history: 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_performance_history 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_performance_history 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_performance_history. 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_performance_history 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 →