Low Risk

getTiktokUsersByHashtags

Search for USERS who authored Tiktok posts tagged with specific hashtags. USE CASE: Find users who have posted content tagged with one or more hashtags. Returns unique, deduplicated user profiles. Pass hashtags as an array of bare alphanumeric strings - do NOT include leading "#". OR semantics: m...

Risk signalsHigh parameter count (13 properties)

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

getTiktokUsersByHashtags 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 getTiktokUsersByHashtags 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 getTiktokUsersByHashtags 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": {
    "getTiktokUsersByHashtags": {}
  }
}

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 getTiktokUsersByHashtags 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 getTiktokUsersByHashtags 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 getTiktokUsersByHashtags tool do? +

Search for USERS who authored Tiktok posts tagged with specific hashtags. USE CASE: Find users who have posted content tagged with one or more hashtags. Returns unique, deduplicated user profiles. Pass hashtags as an array of bare alphanumeric strings - do NOT include leading "#". OR semantics: matches users who posted content tagged with ANY of the listed hashtags. RESPONSE MODES (responseType parameter): "fast" (DEFAULT): Returns up to 300 results directly in one call. Use limit param to reduce. Best for quick lookups. "paging": Async paginated results (100/page). Returns operation ID - call checkOperationStatus to get results. Use pageNumber/tableName for subsequent pages. "csv": Async CSV export. Returns dataDumpExportOperationId - call checkOperationStatus to get S3 download link. Best for bulk export. NOT for keyword/phrase search in descriptions - use getTiktokUsersByKeywords instead. FILTERS: startDate/endDate (YYYY-MM-DD format). OMIT by default. 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 parameter for performance (default: ["id", "username", "nickname"]). AGGREGATE FIELDS (from matching posts) - MUST BE EXPLICITLY REQUESTED IN FIELDS: aggRelevance, relevantPostsCount, relevantPostsLikesSum, relevantPostsCommentsSum, relevantPostsPlaysSum, relevantPostsForwardsSum. 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 getTiktokUsersByHashtags? +

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

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

Can I rate-limit getTiktokUsersByHashtags? +

Yes. Add a rate_limit block to the getTiktokUsersByHashtags 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 getTiktokUsersByHashtags completely? +

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

getTiktokUsersByHashtags 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.