search_content

Search across Metabase content (dashboards, cards, collections)

SERVERMetabase MCP SOURCE1luvc0d3/metabase-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1luvc0d3-metabase-mcp/search-content.md

WHAT IT DOES

What search_content does on Metabase MCP

AI agents call search_content 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.

RISK

Why search_content is rated Low

The tool performs a search operation that retrieves and lists existing Metabase objects. It does not create, modify, delete, or execute anything—it only reads and returns matching content. This is a classic Read category tool with minimal risk unless sensitive dashboards or card metadata should be hidden from the agent.

From the tool's definition Tool name 'search_content' and description 'Search across Metabase content (dashboards, cards, collections)' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_content 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 search_content, this is the rule to start with:

search_content Allowed

search_content is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_content": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every search_content call is checked against it from then on.

FAQ

Questions about search_content

What does the search_content tool do? +

Search across Metabase content (dashboards, cards, collections). It is categorised as a Read tool in the Metabase MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_content? +

Register the Metabase MCP server in PolicyLayer and add a rule for search_content: 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.

What risk level is search_content? +

search_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_content? +

Yes. Add a rate_limit block to the search_content 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.

How do I block search_content completely? +

Set action: deny in the PolicyLayer policy for search_content. 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.

What MCP server provides search_content? +

search_content 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.

KEEP EXPLORING

More on Metabase, and thousands of servers like it.

This server

All 30 Metabase tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →