Retrieve alerts from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Check currently active alerts - Get a list of alerts including closed alerts <examples> Get opening alerts \
AI agents call list_alerts to retrieve information from Mackerel 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 or lists existing alert information from the Mackerel monitoring platform. It has no capability to create, modify, delete, or trigger actions—it only queries and returns data. This is a classic Read operation with low severity since it merely accesses monitoring information already available within the system.
From the tool's definition Tool name 'list_alerts' and description 'Retrieve alerts from Mackerel' indicate a query operation that fetches and returns alert data without modification or side effects.
Documented attack patterns abuse exactly the kind of access list_alerts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mackerel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_alerts:
{
"version": "1",
"default": "deny",
"tools": {
"list_alerts": {}
}
} list_alerts 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.
Retrieve alerts from Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Check currently active alerts - Get a list of alerts including closed alerts <examples> Get opening alerts \. It is categorised as a Read tool in the Mackerel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mackerel MCP Server MCP server in PolicyLayer and add a rule for list_alerts: 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 Mackerel MCP Server. Nothing to install.
list_alerts 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 list_alerts 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 list_alerts. 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.
list_alerts is provided by the Mackerel MCP Server MCP server (mackerelio-labs/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mackerel 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.
16 Mackerel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.