Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by search_creators, semantic_search_creators, autocomplete_creators, or find_lookalike_creators; or - an exact platform+username pair such as pla...
Part of the Influship server.
Free to start. No card required.
AI agents call get_creator 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 get_creator 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": {
"get_creator": {}
}
}See the full Influship policy for all 14 tools.
These attack patterns abuse exactly the kind of access get_creator 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.
Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by search_creators, semantic_search_creators, autocomplete_creators, or find_lookalike_creators; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass include: ['profiles'] to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use get_profile if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use get_profile/get_posts for platform-specific metrics and content if needed. Use lookup_profiles for batch exact profile lookups.. 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 get_creator: 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.
get_creator 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_creator 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_creator. 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_creator 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.