Low Risk

get_stats_distribution

Get alert distribution grouped by category or origin, with filtering, sorting, and pagination

How to control get_stats_distribution ↓

What get_stats_distribution does on RedAlert MCP Server

AI agents call get_stats_distribution to retrieve information from RedAlert MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_stats_distribution needs a policy

This tool retrieves and aggregates historical alert statistics for analysis purposes. It performs no mutations, does not execute commands or external operations, and cannot cause irreversible changes. Filtering, sorting, and pagination are standard read-only query operations. The low severity reflects minimal risk even if misused by an AI agent, as the worst outcome is exposure of alert distribution metadata.

From the tool's definition Tool name 'get_stats_distribution' and description 'Get alert distribution grouped by category or origin, with filtering, sorting, and pagination' indicate a data retrieval operation that returns statistical summaries without modification or execution of…

Documented attack patterns abuse exactly the kind of access get_stats_distribution gives an agent:

How to control get_stats_distribution

PolicyLayer is an MCP gateway — it sits between your AI agents and RedAlert MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stats_distribution:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stats_distribution": {}
  }
}

get_stats_distribution is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register RedAlert MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_stats_distribution

What does the get_stats_distribution tool do? +

Get alert distribution grouped by category or origin, with filtering, sorting, and pagination. It is categorised as a Read tool in the RedAlert MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats_distribution? +

Register the RedAlert MCP Server MCP server in PolicyLayer and add a rule for get_stats_distribution: 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 RedAlert MCP Server. Nothing to install.

What risk level is get_stats_distribution? +

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

Can I rate-limit get_stats_distribution? +

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

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

get_stats_distribution is provided by the RedAlert MCP Server MCP server (ozba/redalert-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RedAlert MCP Server tool call.

Start from RedAlert MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

12 RedAlert MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.