Low Risk

find_lookalike_creators

Find creators SIMILAR to one or more seed creators. Use this when the user already knows a creator they like and wants more like them (e.g., "find creators like @therock", "find more creators like these three I just booked"). Seeds are blended via creator-profile + visual-style + fact embeddings ...

Risk signalsHigh parameter count (14 properties)

Part of the Influship server.

find_lookalike_creators 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 INFLUSHIP →

Free to start. No card required.

AI agents call find_lookalike_creators to retrieve information from Influship 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 find_lookalike_creators 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": {
    "find_lookalike_creators": {}
  }
}

See the full Influship policy for all 14 tools.

Get this rule live on your own Influship server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY INFLUSHIP →

View all 14 tools →

These attack patterns abuse exactly the kind of access find_lookalike_creators 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 find_lookalike_creators only ever does what you allow.

SECURE INFLUSHIP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the find_lookalike_creators tool do? +

Find creators SIMILAR to one or more seed creators. Use this when the user already knows a creator they like and wants more like them (e.g., "find creators like @therock", "find more creators like these three I just booked"). Seeds are blended via creator-profile + visual-style + fact embeddings to surface similar accounts. Seeds are passed in seed_creator_ids (canonical UUIDs) and/or seed_profiles (platform + username; resolve handles via autocomplete_creators first if needed). Returns a ranked list of similar creators with scores. limit caps results (default 25, max 100). Use the flat follower, engagement-rate, and verified fields to constrain results. Use semantic_search_creators instead when you have a topic/niche but no seed. Use match_creators when you have specific candidates and want to score their fit against a brief. Examples: - User: "Find creators like @niickjackson on Instagram" -> use this tool with seed_profiles: [{ platform: "instagram", username: "niickjackson" }]. - User: "Find news creators with 1M+ followers" -> use semantic_search_creators, not this tool.. It is categorised as a Read tool in the Influship MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_lookalike_creators? +

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

What risk level is find_lookalike_creators? +

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

Can I rate-limit find_lookalike_creators? +

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

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

find_lookalike_creators is provided by the Influship MCP server (@influship/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Influship tool call.

Deterministic rules across all 14 Influship 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.