Retrieve sample data from table for preview and analysis - use this to examine content, verify quality, or understand data patterns
AI agents call get_table_data 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 data for informational purposes only. It fetches sample records from a table to enable preview and analysis without modifying, deleting, or executing any operations on the underlying data. The limited scope (sample data, not full dataset extraction) and read-only nature place it firmly in the Read category with low severity.
From the tool's definition Tool description states 'Retrieve sample data from table for preview and analysis' with purposes of examining content, verifying quality, and understanding patterns.
Attacks that exploit this kind of access
Retrieve sample data from table for preview and analysis - use this to examine content, verify quality, or understand data patterns. 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_table_data: 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_table_data 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_table_data 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_table_data. 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_table_data 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 →