Low Risk

get_breakdown

Consolidated breakdown tool. Pick dimension: 'channel' returns per-channel sessions/revenue/RPS plus engagement (visitors, avg dwell seconds, bounce rate) and bot_excluded_count (bot sessions removed from human metrics; a channel with sessions=0 but bot_excluded_count>0 is bot-only traffic, kept ...

Part of the RevenueScope: Japanese EC RPS Benchmarks server.

get_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 REVENUESCOPE: JAPANESE EC RPS BENCHMARKS →

Free to start. No card required.

AI agents call get_breakdown to retrieve information from RevenueScope: Japanese EC RPS Benchmarks 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_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_breakdown": {}
  }
}

See the full RevenueScope: Japanese EC RPS Benchmarks policy for all 7 tools.

Get this rule live on your own RevenueScope: Japanese EC RPS Benchmarks server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY REVENUESCOPE: JAPANESE EC RPS BENCHMARKS →

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

SECURE REVENUESCOPE: JAPANESE EC RPS BENCHMARKS →

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

What does the get_breakdown tool do? +

Consolidated breakdown tool. Pick dimension: 'channel' returns per-channel sessions/revenue/RPS plus engagement (visitors, avg dwell seconds, bounce rate) and bot_excluded_count (bot sessions removed from human metrics; a channel with sessions=0 but bot_excluded_count>0 is bot-only traffic, kept so it is not mistaken for 'no traffic') and — when ad spend is connected (Path B) — spend/ROAS/saturation; plus an 'Unattributed' row (is_unattributed=true) for purchase revenue not tied to any channel, with a revenue_breakdown summary (total_event_jpy/attributed_jpy/unattributed_jpy); pass filter.channel (e.g. 'google','meta','organic_search') to drill into that channel's campaigns (utm_campaign) with RPS/AOV/CVR. 'page' returns per-page pageviews/unique visitors/avg time/bounce ranked by pageviews (limit default 20, max 200; query strings stripped, bots excluded). 'session_attribute' returns the device / time-of-day (4h JST) / day-of-week (ISO) / new-vs-returning breakdowns in one call. site_id is OPTIONAL when OAuth-authenticated. Default period is the last 30 days; pass period='today'/'7d'/'90d' or a raw day count (1-365). filter only applies to dimension='channel'; limit only applies to dimension='page'.. It is categorised as a Read tool in the RevenueScope: Japanese EC RPS Benchmarks MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_breakdown? +

Register the RevenueScope: Japanese EC RPS Benchmarks MCP server in PolicyLayer and add a rule for get_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 RevenueScope: Japanese EC RPS Benchmarks. Nothing to install.

What risk level is get_breakdown? +

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

Can I rate-limit get_breakdown? +

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

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

get_breakdown is provided by the RevenueScope: Japanese EC RPS Benchmarks MCP server (https://mcp.revenuescope.jp/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RevenueScope: Japanese EC RPS Benchmarks tool call.

Deterministic rules across all 7 RevenueScope: Japanese EC RPS Benchmarks 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.