Add gadget to Jira dashboard (POST /rest/api/3/dashboard/{dashboardId}/gadget)
AI agents use addGadgetToDashboard to create or update resources in MCP Atlassian Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Atlassian Server environment.
This tool creates or modifies dashboard state by adding a gadget, which is reversible (gadgets can be removed). It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is moderate because a malicious actor could clutter dashboards or add misleading gadgets, but the impact is limited to UI configuration and does not affect core Jira data or financial systems.
From the tool's definition The tool performs a POST operation to add a gadget to a Jira dashboard (/rest/api/3/dashboard/{dashboardId}/gadget), which modifies the dashboard configuration. The description explicitly indicates this is a creation/addition action (add gadget).
Documented attack patterns abuse exactly the kind of access addGadgetToDashboard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian Server, and nothing reaches the server without passing your rules. This is the rule we recommend for addGadgetToDashboard:
{
"version": "1",
"default": "deny",
"tools": {
"addGadgetToDashboard": {
"limits": [
{
"counter": "addgadgettodashboard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addGadgetToDashboard 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.
Add gadget to Jira dashboard (POST /rest/api/3/dashboard/{dashboardId}/gadget). It is categorised as a Write tool in the MCP Atlassian Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Atlassian Server MCP server in PolicyLayer and add a rule for addGadgetToDashboard: 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 MCP Atlassian Server. Nothing to install.
addGadgetToDashboard 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 addGadgetToDashboard 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 addGadgetToDashboard. 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.
addGadgetToDashboard is provided by the MCP Atlassian Server MCP server (phuc-nt/mcp-atlassian-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 MCP Atlassian Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 MCP Atlassian Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.