Low Risk

get_score_breakdown

Get detailed line-item breakdown for a score dimension

Part of the Ai Visibility Scanner server.

get_score_breakdown 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 AI VISIBILITY SCANNER →

Free to start. No card required.

AI agents call get_score_breakdown to retrieve information from Ai Visibility Scanner 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_score_breakdown 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": {
    "get_score_breakdown": {}
  }
}

See the full Ai Visibility Scanner policy for all 5 tools.

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

ENFORCE ON MY AI VISIBILITY SCANNER →

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

SECURE AI VISIBILITY SCANNER →

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

What does the get_score_breakdown tool do? +

Get detailed line-item breakdown for a score dimension. It is categorised as a Read tool in the Ai Visibility Scanner MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_score_breakdown? +

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

What risk level is get_score_breakdown? +

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

Can I rate-limit get_score_breakdown? +

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

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

get_score_breakdown is provided by the Ai Visibility Scanner MCP server (https://ai-visibility-scanner-production.up.railway.app/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ai Visibility Scanner tool call.

Deterministic rules across all 5 Ai Visibility Scanner 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.