This record as markdown: /tools/1luvc0d3-metabase-mcp/trend-analysis.md
What trend_analysis does on Metabase MCP
AI agents call trend_analysis to retrieve information from Metabase MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why trend_analysis is rated Low
This tool retrieves and analyzes existing time-series data to compute trend metrics, with no side effects on the underlying data. It performs computations on data already accessible via the Metabase server and does not create, modify, delete, or execute external operations.
From the tool's definition Tool name 'trend_analysis' with description 'Identify trends in time-series data' indicates data querying and analysis.
Attacks that exploit this kind of access
The rule that runs trend_analysis safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metabase MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trend_analysis, this is the rule to start with:
trend_analysis is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every trend_analysis call is checked against it from then on.
Questions about trend_analysis
Identify trends in time-series data. It is categorised as a Read tool in the Metabase MCP MCP Server, which means it retrieves data without modifying state.
Register the Metabase MCP server in PolicyLayer and add a rule for trend_analysis: 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. Nothing to install.
trend_analysis 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 trend_analysis 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 trend_analysis. 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.
trend_analysis is provided by the Metabase MCP server (1luvc0d3/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metabase, and thousands of servers like it.
This server
Across the catalogue