Retrieve foreign keys for a card
AI agents call get_card_table_fks to retrieve information from Metabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema metadata (foreign key relationships) without side effects. It performs a simple lookup/query operation on existing database structure, aligning with the 'Read' category definition of retrieving or querying data with no side effects. The severity is low because misuse would only expose schema information, not cause data loss, modification, or execution of arbitrary operations.
From the tool's definition Tool name 'get_card_table_fks' and description 'Retrieve foreign keys for a card' indicate a query operation that fetches metadata about table relationships.
Attacks that exploit this kind of access
Retrieve foreign keys for a card. It is categorised as a Read tool in the Metabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for get_card_table_fks: 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.
get_card_table_fks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_card_table_fks 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 get_card_table_fks. 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.
get_card_table_fks 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 →