Retrieve all dashboards from Mackerel. ๐ USE THIS TOOL WHEN USERS: - Get a list of dashboards - Get ID and title of each dashboard <examples> Get all dashboards \
AI agents call list_dashboards 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 dashboard information from Mackerel's monitoring platform. It performs no side effects, creates no resources, executes no code, deletes nothing, and involves no financial transactions. It is a straightforward data retrieval operation matching the Read category definition.
From the tool's definition Tool name 'list_dashboards' and description 'Retrieve all dashboards from Mackerel' indicate a read-only operation that queries and returns dashboard data without modifying anything.
Documented attack patterns abuse exactly the kind of access list_dashboards 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_dashboards:
{
"version": "1",
"default": "deny",
"tools": {
"list_dashboards": {}
}
} list_dashboards 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 all dashboards from Mackerel. ๐ USE THIS TOOL WHEN USERS: - Get a list of dashboards - Get ID and title of each dashboard <examples> Get all dashboards \. 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_dashboards: 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_dashboards 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_dashboards 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_dashboards. 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_dashboards 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.