Generate a publicly accessible URL for a Metabase card that can be viewed without authentication (requires admin privileges) - use this to share analytical insights with external stakeholders, create public reports, or embed charts in websites
AI agents use create_card_public_link 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.
This tool creates or modifies sharing settings by generating public links—a reversible write operation rather than a read-only query. While it doesn't delete or execute arbitrary code, it does change the visibility/access state of an asset. The blast radius is medium: misconfiguration could expose sensitive analytics publicly, but the effect is reversible (the link can be revoked/deleted).
From the tool's definition Tool description states it 'Generate[s] a publicly accessible URL for a Metabase card' and 'share[s] analytical insights with external stakeholders, create[s] public reports', which are write/modification operations that create new public sharing links.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Generate a publicly accessible URL for a Metabase card that can be viewed without authentication (requires admin privileges) - use this to share analytical insights with external stakeholders, create public reports, or embed charts in websites. 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 create_card_public_link: 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.
create_card_public_link 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 create_card_public_link 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 create_card_public_link. 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.
create_card_public_link 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 →