Autocomplete creator names, usernames, or display names from partial input. Use this for fast lookup when the user types a partial handle or name and you need to resolve it to canonical creator IDs (e.g., "find @cris" or "who's that fitness coach called Jane?"). Cheap and fast — prefer over searc...
Part of the Influship server.
Free to start. No card required.
AI agents call autocomplete_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 autocomplete_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.
{
"version": "1",
"default": "deny",
"tools": {
"autocomplete_creators": {}
}
}See the full Influship policy for all 14 tools.
These attack patterns abuse exactly the kind of access autocomplete_creators gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Autocomplete creator names, usernames, or display names from partial input. Use this for fast lookup when the user types a partial handle or name and you need to resolve it to canonical creator IDs (e.g., "find @cris" or "who's that fitness coach called Jane?"). Cheap and fast — prefer over search_creators for handle-style queries where the user already knows roughly who they want. Use get_profile instead when the user gives an exact platform+username pair. Use search_creators for the same fuzzy creator lookup behavior with a less typeahead- specific name. Use semantic_search_creators only for discovery by topic, niche, audience, geography, or content style, not for resolving a known creator. Examples: - User: "Who is that fitness coach called Jane?" -> use this tool. - User: "Find @cris..." -> use this tool to resolve the partial handle. - User: "Pull @niickjackson on Instagram" -> use get_profile, not this tool. Returns a short list of matching creators with their IDs, platforms, and display names. Use the IDs returned here as input to get_creator, find_lookalike_creators, or match_creators for downstream operations.. It is categorised as a Read tool in the Influship MCP Server, which means it retrieves data without modifying state.
Register the Influship MCP server in PolicyLayer and add a rule for autocomplete_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.
autocomplete_creators 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 autocomplete_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.
Set action: deny in the PolicyLayer policy for autocomplete_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.
autocomplete_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.
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.