# tiktok_ads_rf_inventory_estimate Reach & Frequency INVENTORY ESTIMATE — how many people TikTok can reach, for what budget, at what frequency, over a fixed window, before anything is booked. THIS IS THE ONLY SANCTIONED SOURCE of the three numbers create_tiktok_ads_rf_ad_group needs (budget, purchasedImpression, purchasedReach), and that matters because TikTok does NOT refuse a reservation outside the range it estimated — it silently books its own maximum instead, so an invented number buys something nobody asked for. IMPRESSIONS AND REACH COME BACK IN THOUSANDS (110 means 110,000) and the create takes the same unit, so pass them back UNSCALED. Fix ONE of the three with rfPurchasedType (FIXED_BUDGET / FIXED_SHOW / FIXED_REACH) and TikTok predicts the other two; omit it to get the whole range. Reach & Frequency is ALLOWLIST-ONLY per ad account. Read-only, free, books nothing. Agent View of the PolicyLayer registry record for `tiktok_ads_rf_inventory_estimate`. HTML page: https://policylayer.com/tools/hermoso/tiktok-ads-rf-inventory-estimate ## Facts - Tool: `tiktok_ads_rf_inventory_estimate` - Server: Hermoso (`https://app.hermoso.ai/mcp`) — https://policylayer.com/tools/hermoso.md - Homepage: git+https://github.com/hermoso-ai/hermoso.git - Risk category: Write (Medium risk) - Registry record: grade D, identity unverified - Server auth posture: gated - Server CORS policy: * - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "tiktok_ads_rf_inventory_estimate", "arguments": {} } } ``` ## Why tiktok_ads_rf_inventory_estimate is rated Medium An AI agent can call tiktok_ads_rf_inventory_estimate faster than any human can review: one bad instruction and it creates or modifies resources in Hermoso by the hundred, each call as confident as the last. ## Use case AI agents use tiktok_ads_rf_inventory_estimate to create or update resources in Hermoso, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hermoso environment. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hermoso: ```json { "version": "1", "default": "deny", "tools": { "tiktok_ads_rf_inventory_estimate": { "limits": [ { "counter": "tiktok_ads_rf_inventory_estimate_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Hermoso (895) - `answer_google_business_question` — Destructive — https://policylayer.com/tools/hermoso/answer-google-business-question.md - `apple_ads_change_history` — Destructive — https://policylayer.com/tools/hermoso/apple-ads-change-history.md - `associate_linkedin_conversion_campaigns` — Destructive — https://policylayer.com/tools/hermoso/associate-linkedin-conversion-campaigns.md - `cancel_openai_ads_audience_operation` — Destructive — https://policylayer.com/tools/hermoso/cancel-openai-ads-audience-operation.md - `cancel_scheduled` — Destructive — https://policylayer.com/tools/hermoso/cancel-scheduled.md - `cancel_stripe_subscription` — Destructive — https://policylayer.com/tools/hermoso/cancel-stripe-subscription.md - `clear_sheet_range` — Destructive — https://policylayer.com/tools/hermoso/clear-sheet-range.md - `create_analytics_custom_dimension` — Destructive — https://policylayer.com/tools/hermoso/create-analytics-custom-dimension.md - `create_openai_ads_campaign` — Destructive — https://policylayer.com/tools/hermoso/create-openai-ads-campaign.md - `delete_analytics_key_event` — Destructive — https://policylayer.com/tools/hermoso/delete-analytics-key-event.md - `delete_apple_ads_object` — Destructive — https://policylayer.com/tools/hermoso/delete-apple-ads-object.md - `delete_bluesky_post` — Destructive — https://policylayer.com/tools/hermoso/delete-bluesky-post.md - `delete_brand` — Destructive — https://policylayer.com/tools/hermoso/delete-brand.md - `delete_creator` — Destructive — https://policylayer.com/tools/hermoso/delete-creator.md - `delete_dm_automation` — Destructive — https://policylayer.com/tools/hermoso/delete-dm-automation.md - `delete_drive_file` — Destructive — https://policylayer.com/tools/hermoso/delete-drive-file.md - `delete_google_ads_object` — Destructive — https://policylayer.com/tools/hermoso/delete-google-ads-object.md - `delete_google_business_post` — Destructive — https://policylayer.com/tools/hermoso/delete-google-business-post.md - `delete_instagram_dm_automation` — Destructive — https://policylayer.com/tools/hermoso/delete-instagram-dm-automation.md - `delete_linkedin_ads_object` — Destructive — https://policylayer.com/tools/hermoso/delete-linkedin-ads-object.md - `delete_linkedin_comment` — Destructive — https://policylayer.com/tools/hermoso/delete-linkedin-comment.md - `delete_linkedin_lead_subscription` — Destructive — https://policylayer.com/tools/hermoso/delete-linkedin-lead-subscription.md - `delete_merchant_data_source` — Destructive — https://policylayer.com/tools/hermoso/delete-merchant-data-source.md - `delete_merchant_product` — Destructive — https://policylayer.com/tools/hermoso/delete-merchant-product.md - `delete_messenger_marketing_campaign` — Destructive — https://policylayer.com/tools/hermoso/delete-messenger-marketing-campaign.md - `delete_meta_audience` — Destructive — https://policylayer.com/tools/hermoso/delete-meta-audience.md - `delete_meta_catalog` — Destructive — https://policylayer.com/tools/hermoso/delete-meta-catalog.md - `delete_meta_object` — Destructive — https://policylayer.com/tools/hermoso/delete-meta-object.md - `delete_microsoft_ads_object` — Destructive — https://policylayer.com/tools/hermoso/delete-microsoft-ads-object.md - `delete_microsoft_merchant_product` — Destructive — https://policylayer.com/tools/hermoso/delete-microsoft-merchant-product.md - …and 865 more: https://policylayer.com/tools/hermoso.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=hermoso · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/hermoso