Score how well specific creators fit a campaign brief or search intent. Use this when the user already has candidate creators in mind and wants to evaluate fit (e.g., "rate these 5 creators for a vegan cookbook launch", "which of these is the best match for my crypto audience?"). For each creator...
Part of the Influship server.
Free to start. No card required.
AI agents call match_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 match_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": {
"match_creators": {}
}
}See the full Influship policy for all 14 tools.
These attack patterns abuse exactly the kind of access match_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.
Score how well specific creators fit a campaign brief or search intent. Use this when the user already has candidate creators in mind and wants to evaluate fit (e.g., "rate these 5 creators for a vegan cookbook launch", "which of these is the best match for my crypto audience?"). For each creator the API returns a match score (0-1), a good/neutral/avoid decision, and structured reasons. Pass candidates in creator_ids (canonical UUIDs) and/or profiles (platform + username). intent_query is the brief the LLM reasons against; intent_context is optional extra context (target audience, brand values, prior collabs). Use semantic_search_creators when you don't have candidates yet and need topical or niche discovery. Use search_creators first when you only need to resolve rough creator names/handles into candidates. Use find_lookalike_creators when you want creators similar to known good fits. Examples: - User: "Is @niickjackson a fit for Pixel?" -> use this tool after resolving the exact Instagram profile with get_profile; call get_posts first if recent content context is needed. - User: "Rate these five creators for a vegan cookbook launch" -> use this tool.. 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 match_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.
match_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 match_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 match_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.
match_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.