infra.cloudflare.zone_analytics
Traffic analytics for a Cloudflare zone — total requests, cached vs uncached, bandwidth, threats blocked, page views. Supports custom time ranges (last 24h, 7 days, etc.) (Cloudflare)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/infra.cloudflare.zone-analytics.md
What infra.cloudflare.zone_analytics does on Apibase
AI agents call infra.cloudflare.zone_analytics to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
since | integer | — | Minutes ago to start from (e.g. -1440 for last 24h, -10080 for last 7 days) |
zone_id | string | Yes | Cloudflare Zone ID |
Parameters from the server's own tool schema.
Why infra.cloudflare.zone_analytics is rated Low
Retrieves analytics data without modifying infrastructure, credentials, or configuration; informational only.
From the tool's definition Traffic analytics for a Cloudflare zone — total requests, cached vs uncached, bandwidth, threats blocked
Attacks that exploit this kind of access
The rule that runs infra.cloudflare.zone_analytics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infra.cloudflare.zone_analytics, this is the rule to start with:
infra.cloudflare.zone_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every infra.cloudflare.zone_analytics call is checked against it from then on.
Questions about infra.cloudflare.zone_analytics
Traffic analytics for a Cloudflare zone — total requests, cached vs uncached, bandwidth, threats blocked, page views. Supports custom time ranges (last 24h, 7 days, etc.) (Cloudflare). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
infra.cloudflare.zone_analytics accepts 2 parameters: since, zone_id. Required: zone_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for infra.cloudflare.zone_analytics: 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 Apibase. Nothing to install.
infra.cloudflare.zone_analytics 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 infra.cloudflare.zone_analytics 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 infra.cloudflare.zone_analytics. 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.
infra.cloudflare.zone_analytics is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue