Start a live stream on TikVid. Followers get notified.
AI agents invoke start_live to trigger actions in TikVid MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
start_live executes an operational command that initiates a live broadcast and notification system. While not destructive or financial, it triggers external actions and state changes (stream goes live, notifications sent) that represent real-world effects.
From the tool's definition Tool performs 'Start a live stream' with side effects: it triggers a broadcast action and initiates notifications to followers ('Followers get notified'). This is an external operation whose effects depend on execution, not a data read or reversible write.
Attacks that exploit this kind of access
Start a live stream on TikVid. Followers get notified. It is categorised as a Execute tool in the TikVid MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TikVid MCP Server MCP server in PolicyLayer and add a rule for start_live: 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 TikVid MCP Server. Nothing to install.
start_live is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_live 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 start_live. 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.
start_live is provided by the TikVid MCP Server MCP server (liortesta/tikvid). 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 →