AI agents use reposition_dashboard_cards to create or update resources in Metabase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase environment.
The tool modifies the state of dashboard cards by changing their positions—a reversible data modification operation. This is Write category (not Destructive, as repositioning is undoable). Severity is medium because misuse could disrupt dashboard usability for multiple users, but data integrity remains intact.
From the tool's definition Tool name 'reposition_dashboard_cards' indicates modification of dashboard card layout/positioning. Sibling tools include create_card, create_dashboard, execute_card which are Write/Execute operations on Metabase dashboards.
Attacks that exploit this kind of access
reposition_dashboard_cards. It is categorised as a Write tool in the Metabase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metabase MCP server in PolicyLayer and add a rule for reposition_dashboard_cards: 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 Metabase. Nothing to install.
reposition_dashboard_cards 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 reposition_dashboard_cards 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 reposition_dashboard_cards. 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.
reposition_dashboard_cards is provided by the Metabase MCP server (voducdan/matebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →