get_site_analytics

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/get-site-analytics.md

WHAT IT DOES

What get_site_analytics does on Meta Council

AI agents call get_site_analytics to retrieve information from Meta Council 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
`days`	integer	—	Whole UTC days to cover, ending today. Defaults to 7.
`digest_limit`	integer	—
`digest_before_week`	string	—

Parameters from the server's own tool schema.

RISK

Why get_site_analytics is rated Low

Even though get_site_analytics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_site_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_site_analytics, this is the rule to start with:

get_site_analytics Allowed

get_site_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_site_analytics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every get_site_analytics call is checked against it from then on.

FAQ

Questions about get_site_analytics

What does the get_site_analytics tool do? +

OPERATOR ONLY: visitor traffic for the META COUNCIL PLATFORM's own website — every visitor added together, NOT the caller's workspace (use get_workspace_metrics for that) and NOT the business rollup (use get_meta_council_platform_metrics for that). Requires both the platform:admin scope AND an ADMIN_EMAILS operator account; everyone else gets a permission error naming which of the two requirements failed. Covers a window of whole UTC days ending today, set by days. Returns human total views, unique visitors, the authenticated/anonymous split, the busiest public paths, the busiest in-app sections, top referrers and a per-day series, separate bot page/section view counts, plus the window it covers so the caller need not track what it asked for. Page paths and in-app sections are counted separately and are not comparable to one another. It never returns per-visitor rows, email addresses, IP hashes, user agents, session identifiers or query text — the rollup reports how many, never who. Also returns recorded account activation cohorts by creation-event source and signed-in weekly distinct account/section usage. These are prospective observations, not visitor conversion: campaign attribution, visit-to-account conversion and visit entry pages are explicitly unavailable. No named account activity is returned. Optional digest_limit includes retained weekly aggregate snapshots and delivery counts; digest_before_week pages strictly before a scheduled Monday YYYY-MM-DD. This read never captures or sends a digest. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does get_site_analytics accept? +

get_site_analytics accepts 3 parameters: days, digest_limit, digest_before_week. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_site_analytics? +

Register the Meta Council MCP server in PolicyLayer and add a rule for get_site_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 Meta Council. Nothing to install.

What risk level is get_site_analytics? +

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

Can I rate-limit get_site_analytics? +

Yes. Add a rate_limit block to the get_site_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.

How do I block get_site_analytics completely? +

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

What MCP server provides get_site_analytics? +

get_site_analytics is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →