pages.statistics
Get CDN traffic for one static website this Vee3 account hosts. Returns request count, bandwidth, cache hit rate, and bandwidth by country for a UTC date range. Request count includes every file the CDN served, not unique visitors. The range is inclusive. When the user or agent omits dates, the l...
This record as markdown: /tools/io-github-vee3io-vee3/pages.statistics.md
What pages.statistics does on Vee3
AI agents call pages.statistics to retrieve information from Vee3 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 |
|---|---|---|---|
date_to | object | — | Inclusive UTC end date (YYYY-MM-DD). Defaults to today UTC. |
page_id | string | Yes | Page id returned by pages.create. |
date_from | object | — | Inclusive UTC start date (YYYY-MM-DD). Defaults to 6 days before date_to. |
Parameters from the server's own tool schema.
Why pages.statistics is rated Low
Retrieves historical analytics data about website traffic with no side effects or modifications.
From the tool's definition Get CDN traffic, request count, bandwidth, cache hit rate statistics
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs pages.statistics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pages.statistics, this is the rule to start with:
pages.statistics 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 Vee3, apply this rule, and every pages.statistics call is checked against it from then on.
Questions about pages.statistics
Get CDN traffic for one static website this Vee3 account hosts. Returns request count, bandwidth, cache hit rate, and bandwidth by country for a UTC date range. Request count includes every file the CDN served, not unique visitors. The range is inclusive. When the user or agent omits dates, the last 7 UTC days including today are used. The range can be at most 31 days. Cost = 10 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
pages.statistics accepts 3 parameters: date_to, page_id, date_from. Required: page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for pages.statistics: 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 Vee3. Nothing to install.
pages.statistics 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 pages.statistics 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 pages.statistics. 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.
pages.statistics is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue