Get detailed historical alert records with full city data, filtering, sorting, and pagination
AI agents call get_stats_history 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.
This tool retrieves and queries historical alert statistics and city data. It performs no mutations, deletions, or external operations—only data retrieval with standard query parameters (filtering, sorting, pagination). This is a classic Read operation with minimal risk if misused by an AI agent, as it cannot alter state or trigger alerts.
From the tool's definition Tool name 'get_stats_history' and description 'Get detailed historical alert records' indicate retrieval of existing data.
Documented attack patterns abuse exactly the kind of access get_stats_history gives an agent:
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_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_stats_history": {}
}
}get_stats_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed historical alert records with full city data, 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.
Register the RedAlert MCP Server MCP server in PolicyLayer and add a rule for get_stats_history: 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.
get_stats_history 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 get_stats_history 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 get_stats_history. 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.
get_stats_history 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.
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.