Retrieve a specific alert by ID from Mackerel. ๐ USE THIS TOOL WHEN USERS: - Investigate a particular alert <examples> Get alert by ID \
AI agents call get_alert 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/queries alert information by ID from the Mackerel monitoring platform with no side effects. It does not create, modify, delete, execute external operations, or commit financial obligations. The context shows it is part of a monitoring platform's read operations alongside similar tools like get_dashboard, get_host_metrics, and get_trace.
From the tool's definition Tool name 'get_alert' and description 'Retrieve a specific alert by ID from Mackerel' indicate retrieval of existing data without modification.
Documented attack patterns abuse exactly the kind of access get_alert 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 get_alert:
{
"version": "1",
"default": "deny",
"tools": {
"get_alert": {}
}
} get_alert 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 a specific alert by ID from Mackerel. ๐ USE THIS TOOL WHEN USERS: - Investigate a particular alert <examples> Get alert by ID \. 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 get_alert: 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.
get_alert 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 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. 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 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.