New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_meta_council_platform_metrics

OPERATOR ONLY: cross-owner analytics for the META COUNCIL PLATFORM itself — every account added together, NOT the caller's workspace (use get_workspace_metrics for that). Requires both the platform:admin scope AND an ADMIN_EMAILS operator account; everyone else gets a permission error. Returns co...

SERVERMeta Council SOURCEhttps://meta-council.com/mcp
Low RISK CLASS
Category Read
Parameters 00 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-meta-council-platform-metrics.md

What get_meta_council_platform_metrics does on Meta Council

AI agents call get_meta_council_platform_metrics 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.

Why get_meta_council_platform_metrics is rated Low

Even though get_meta_council_platform_metrics 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

Questions about get_meta_council_platform_metrics

What does the get_meta_council_platform_metrics tool do? +

OPERATOR ONLY: cross-owner analytics for the META COUNCIL PLATFORM itself — every account added together, NOT the caller's workspace (use get_workspace_metrics for that). Requires both the platform:admin scope AND an ADMIN_EMAILS operator account; everyone else gets a permission error. Returns content-free aggregates only: account counts, 30-day active owners, session counts by status and token totals, ticket open/done, deal pipeline and outstanding invoice amounts separated by recorded currency without FX conversion and with missing coverage stated, overdue invoice counts, feedback backlog, per-pillar adoption, the busiest panel slugs, and a per-account activity table (email and counts). It never returns query text, answers, feedback bodies, deal or invoice detail, or any other text a user typed — the aggregate reports how much, never what about. Note that open + done need not equal the ticket total: cancelled tickets are neither. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_meta_council_platform_metrics? +

Register the Meta Council MCP server in PolicyLayer and add a rule for get_meta_council_platform_metrics: 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_meta_council_platform_metrics? +

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

Can I rate-limit get_meta_council_platform_metrics? +

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

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

get_meta_council_platform_metrics 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meta Council's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.