Low Risk

botindex_zora_creator_scores

Get creator performance scores on Zora. Identifies top-performing creators by attention metrics and coin success rates. $0.03

Part of the Botindex server.

botindex_zora_creator_scores 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 BOTINDEX →

Free to start. No card required.

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

See the full Botindex policy for all 23 tools.

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

ENFORCE ON MY BOTINDEX →

View all 23 tools →

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

SECURE BOTINDEX →

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

What does the botindex_zora_creator_scores tool do? +

Get creator performance scores on Zora. Identifies top-performing creators by attention metrics and coin success rates. $0.03. It is categorised as a Read tool in the Botindex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on botindex_zora_creator_scores? +

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

What risk level is botindex_zora_creator_scores? +

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

Can I rate-limit botindex_zora_creator_scores? +

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

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

botindex_zora_creator_scores is provided by the Botindex MCP server (botindex-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Botindex tool call.

Deterministic rules across all 23 Botindex 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.