get_sales_analytics

Sales pipeline analytics for the caller: probability-weighted forecast, per-stage $ rollup, win rate (won / decided, by count and by value), average sales-cycle days over won deals, and open-deal aging with a stale count. Read-only; computed from the caller's own deals. Requires authentication.

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-sales-analytics.md

WHAT IT DOES

What get_sales_analytics does on Meta Council

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

RISK

Why get_sales_analytics is rated Low

This is a retrieval and aggregation tool that queries and presents sales data metrics. It performs no side effects, creates no data, executes no operations, and is restricted to the authenticated caller's own deal information.

From the tool's definition Tool description explicitly states 'Read-only; computed from the caller's own deals.' Returns analytics metrics: 'probability-weighted forecast, per-stage $ rollup, win rate, average sales-cycle days, open-deal aging.' No modification, deletion, or execution…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_sales_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_sales_analytics, this is the rule to start with:

get_sales_analytics Allowed

get_sales_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_sales_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_sales_analytics call is checked against it from then on.

FAQ

Questions about get_sales_analytics

What does the get_sales_analytics tool do? +

How do I enforce a policy on get_sales_analytics? +

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

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

Can I rate-limit get_sales_analytics? +

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

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

get_sales_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_product_sales on 08-AI-Business-Agent →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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