New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_tiktok_tto_spark_authorization

Whether a creator has approved Spark Ads authorization for their video, and if so the authorization CODE, the window it covers, and whether that code is already bound to an ad account. The code is what authorize_tiktok_ads_spark_post takes. It appears only once the creator accepts: nothing on thi...

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/get-tiktok-tto-spark-authorization.md

What get_tiktok_tto_spark_authorization does on Hermoso

AI agents call get_tiktok_tto_spark_authorization to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_tiktok_tto_spark_authorization is rated Low

Even though get_tiktok_tto_spark_authorization only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about get_tiktok_tto_spark_authorization

What does the get_tiktok_tto_spark_authorization tool do? +

Whether a creator has approved Spark Ads authorization for their video, and if so the authorization CODE, the window it covers, and whether that code is already bound to an ad account. The code is what authorize_tiktok_ads_spark_post takes. It appears only once the creator accepts: nothing on this side can produce one; and TikTok also reports how many further requests are left. Read-only, free. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tiktok_tto_spark_authorization? +

Register the Hermoso MCP server in PolicyLayer and add a rule for get_tiktok_tto_spark_authorization: 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 Hermoso. Nothing to install.

What risk level is get_tiktok_tto_spark_authorization? +

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

Can I rate-limit get_tiktok_tto_spark_authorization? +

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

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

get_tiktok_tto_spark_authorization is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hermoso, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hermoso's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.