Check the current real-time alert subscription status including connection state, subscribed types, and buffer size.
AI agents call get_alert_subscription_status 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 subscription metadata and connection status. It performs no writes, deletes, executions, or financial transactions. The operation is read-only and informational, returning existing state without altering system behavior. Severity is low as misuse poses minimal risk—an agent querying subscription status cannot cause harm.
From the tool's definition Tool name 'get_alert_subscription_status' and description 'Check the current real-time alert subscription status' indicate a retrieval operation that queries subscription state without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_alert_subscription_status 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_alert_subscription_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_alert_subscription_status": {}
}
}get_alert_subscription_status 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.
Check the current real-time alert subscription status including connection state, subscribed types, and buffer size. 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_alert_subscription_status: 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_alert_subscription_status 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_alert_subscription_status 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_alert_subscription_status. 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_alert_subscription_status 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.