Returns a small number of opening hook examples (the first 3 seconds of a reel — the line that stops the scroll) for a medical or dental practice niche. Use this when someone asks for hook ideas, opening lines, or scroll-stoppers. Hooks are extracted from the Cakesmash 30 Reel Scripts packs — eve...
AI agents call get_hook_examples to retrieve information from Cakesmash without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | number | — | How many hooks to return (1-5). Defaults to 3. |
niche | string | — | The practice type. See get_reel_script_sample for niche definitions. |
Parameters from the server's own tool schema.
This tool performs a simple read operation: querying and returning example marketing content (hook scripts) for dental/medical practices. There are no side effects, no data modification, no code execution, and no destructive actions.
From the tool's definition Tool returns hook examples and opening lines from a database — 'Returns a small number of opening hook examples' — with no modification, deletion, or execution capability.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_hook_examples gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cakesmash, and nothing reaches the server without passing your rules. This is the rule we recommend for get_hook_examples:
{
"version": "1",
"default": "deny",
"tools": {
"get_hook_examples": {}
}
}get_hook_examples is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns a small number of opening hook examples (the first 3 seconds of a reel — the line that stops the scroll) for a medical or dental practice niche. Use this when someone asks for hook ideas, opening lines, or scroll-stoppers. Hooks are extracted from the Cakesmash 30 Reel Scripts packs — every hook has been pressure-tested for specificity and patient-decision pull. It is categorised as a Read tool in the Cakesmash MCP Server, which means it retrieves data without modifying state.
get_hook_examples accepts 2 parameters: count, niche. The full parameter table on this page comes from the server's own tool schema.
Register the Cakesmash MCP server in PolicyLayer and add a rule for get_hook_examples: 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 Cakesmash. Nothing to install.
get_hook_examples is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_hook_examples 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 get_hook_examples. 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.
get_hook_examples is provided by the Cakesmash MCP server (kylecassie/cakesmash-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cakesmash, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Cakesmash tools catalogued and risk-classified — across an index of 43,000+ MCP servers.