Low Risk

getTiktokCommentsByPostId

Get COMMENT CONTENT (text, likes) for a Tiktok post. Returns the actual comment objects with text and metadata. RETURNS COMMENT DATA: id, text, username, createdAtDate, likeCount. Use for reading what people said. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results...

Risk signalsHigh parameter count (13 properties)

Part of the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) server.

getTiktokCommentsByPostId is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE SOCIAL MEDIA SEARCH API — TWITTER, INSTAGRAM, REDDIT, TIKTOK (XPOZ) →

Free to start. No card required.

AI agents call getTiktokCommentsByPostId to retrieve information from Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though getTiktokCommentsByPostId only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTiktokCommentsByPostId": {}
  }
}

See the full Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) policy for all 48 tools.

Get this rule live on your own Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SOCIAL MEDIA SEARCH API — TWITTER, INSTAGRAM, REDDIT, TIKTOK (XPOZ) →

View all 48 tools →

These attack patterns abuse exactly the kind of access getTiktokCommentsByPostId gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so getTiktokCommentsByPostId only ever does what you allow.

SECURE SOCIAL MEDIA SEARCH API — TWITTER, INSTAGRAM, REDDIT, TIKTOK (XPOZ) →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the getTiktokCommentsByPostId tool do? +

Get COMMENT CONTENT (text, likes) for a Tiktok post. Returns the actual comment objects with text and metadata. RETURNS COMMENT DATA: id, text, username, createdAtDate, likeCount. Use for reading what people said. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. PAGING (responseType="paging"): Async paginated results (100/page), returns operationId for polling via checkOperationStatus. Supports pageNumber/tableName for subsequent pages. CSV (responseType="csv"): Async single CSV download, returns operationId, poll for S3 link. CODE EXECUTION: For csv mode, download CSV and use code execution to analyze full dataset. Ideal for: sentiment analysis, reading discussions, analyzing comment content, engagement patterns. Date filters: OMIT startDate/endDate by default. ONLY pass if user explicitly requests date range. IMPORTANT!!!!!: THE CURRENT YEAR IS 2026. When user requests relative dates (last week, last month), verify the current date from your system context and double-check the calculated dates - models often get the year wrong, searching one year earlier than intended. Optional fields: ["id", "text", "username", "createdAtDate", "likeCount"]. This is a safe, read-only tool for analyzing searchable information.. It is categorised as a Read tool in the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTiktokCommentsByPostId? +

Register the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server in PolicyLayer and add a rule for getTiktokCommentsByPostId: 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 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ). Nothing to install.

What risk level is getTiktokCommentsByPostId? +

getTiktokCommentsByPostId is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getTiktokCommentsByPostId? +

Yes. Add a rate_limit block to the getTiktokCommentsByPostId 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.

How do I block getTiktokCommentsByPostId completely? +

Set action: deny in the PolicyLayer policy for getTiktokCommentsByPostId. 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.

What MCP server provides getTiktokCommentsByPostId? +

getTiktokCommentsByPostId is provided by the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server (https://mcp.xpoz.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) tool call.

Deterministic rules across all 48 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.