Update a specific dashboard by ID in Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Modify dashboard title, memo, or URL path - Update dashboard widgets configuration <examples> Update dashboard \
AI agents use update_dashboard to create or update resources in Mackerel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mackerel MCP Server environment.
This tool modifies dashboard metadata and configuration in a monitoring platform. These are write operations that create or update data reversibly. While dashboards are typically not critical systems, unauthorized modifications could disrupt monitoring visibility. The impact is bounded to dashboard configuration without affecting monitored systems themselves, warranting medium severity rather than high.
From the tool's definition Tool name is 'update_dashboard' and description states 'Update a specific dashboard by ID in Mackerel.' The examples show modifying dashboard title, memo, URL path, and widgets configuration—all reversible changes to dashboard configuration.
Documented attack patterns abuse exactly the kind of access update_dashboard 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 update_dashboard:
{
"version": "1",
"default": "deny",
"tools": {
"update_dashboard": {
"limits": [
{
"counter": "update_dashboard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_dashboard stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update a specific dashboard by ID in Mackerel. 🔍 USE THIS TOOL WHEN USERS: - Modify dashboard title, memo, or URL path - Update dashboard widgets configuration <examples> Update dashboard \. It is categorised as a Write tool in the Mackerel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mackerel MCP Server MCP server in PolicyLayer and add a rule for update_dashboard: 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.
update_dashboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_dashboard 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 update_dashboard. 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.
update_dashboard 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.