Bulk transfer multiple Metabase cards to a specific collection for organizational purposes - use this to categorize cards by team, project, or topic, or to implement content governance policies
AI agents use move_cards_to_collection to create or update resources in Metabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP Server environment.
The tool modifies card locations and metadata within Metabase collections (a write operation) but does not delete, destroy, execute code, or trigger financial transactions. The effects are reversible—cards can be moved again. Severity is medium because misuse could disrupt team workflows and content governance by misplacing or hiding analytics cards, but the data itself remains intact and recoverable.
From the tool's definition Tool enables 'Bulk transfer multiple Metabase cards to a specific collection', modifying the organizational structure and location metadata of cards.
Attacks that exploit this kind of access
Bulk transfer multiple Metabase cards to a specific collection for organizational purposes - use this to categorize cards by team, project, or topic, or to implement content governance policies. It is categorised as a Write tool in the Metabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for move_cards_to_collection: 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 MCP Server. Nothing to install.
move_cards_to_collection 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 move_cards_to_collection 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 move_cards_to_collection. 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.
move_cards_to_collection is provided by the Metabase MCP Server MCP server (thangnm93/metabase-mcp-server). 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 →