recommend_panel
Recommend the best expert panel for a query (semantic match with keyword fallback). Returns the top panel + confidence and the runner-up options — feed the result into run_council's panel argument. Requires authentication because the query may be sent to the configured embedding provider.
This record as markdown: /tools/com-meta-council-decision-intelligence/recommend-panel.md
What recommend_panel does on Meta Council
AI agents call recommend_panel to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | The question or decision to match to a panel. |
Parameters from the server's own tool schema.
Why recommend_panel is rated Low
This tool retrieves and queries data about expert panels based on semantic similarity to a user query. It has no side effects—it reads configuration, performs a lookup operation, and returns results. The authentication requirement is for data transmission safety, not evidence of state modification. The lack of side effects and read-only nature clearly places it in the Read category with low severity.
From the tool's definition Tool description states it 'Recommend[s] the best expert panel for a query' and 'Returns the top panel + confidence and the runner-up options'.
Attacks that exploit this kind of access
The rule that runs recommend_panel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recommend_panel, this is the rule to start with:
recommend_panel 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 Meta Council, apply this rule, and every recommend_panel call is checked against it from then on.
Questions about recommend_panel
Recommend the best expert panel for a query (semantic match with keyword fallback). Returns the top panel + confidence and the runner-up options — feed the result into run_council's panel argument. Requires authentication because the query may be sent to the configured embedding provider. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
recommend_panel accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for recommend_panel: 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 Meta Council. Nothing to install.
recommend_panel 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 recommend_panel 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 recommend_panel. 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.
recommend_panel is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue