query_sme
Query an external Subject Matter Expert (SME) AI for verified domain knowledge. The SME's answers are grounded in verified rules and go through a rigorous verification pipeline — this is NOT a general search, it's consulting a domain expert. Use this when: - You need factual, verified information...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/query-sme.md
What query_sme does on Freedom Mcp
AI agents call query_sme to retrieve information from Freedom Mcp 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 |
|---|---|---|---|
context | string | — | Optional context about why you're asking — helps the SME give a more relevant answer. E.g., "I'm creating a social media post about cleanroom best practices" |
question | string | Yes | The question to ask the subject matter expert. Be specific and clear. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
sme_source | string | — | Which Expert to consult, by key. "conduit" (pharmaceutical compounding compliance) is always available; your company may have additional Experts configured. Def |
Parameters from the server's own tool schema.
Why query_sme is rated Low
This tool retrieves verified information from an external SME system for consultation and content creation purposes. It performs no data modification, deletion, code execution, or financial operations. The emphasis on 'verified' and 'grounded in' suggests it returns structured knowledge rather than executing arbitrary operations.
From the tool's definition Tool description states 'Query an external Subject Matter Expert (SME) AI for verified domain knowledge' and use cases include 'need factual, verified information', 'fact-check a claim', 'need talking points' — all read-only retrieval operations with no side…
Attacks that exploit this kind of access
The rule that runs query_sme safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_sme, this is the rule to start with:
query_sme 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 Freedom Mcp, apply this rule, and every query_sme call is checked against it from then on.
Questions about query_sme
Query an external Subject Matter Expert (SME) AI for verified domain knowledge. The SME's answers are grounded in verified rules and go through a rigorous verification pipeline — this is NOT a general search, it's consulting a domain expert. Use this when: - You need factual, verified information for content creation (social media, blog posts, newsletters) - You want to fact-check a claim before publishing - You need talking points grounded in domain expertise - You're creating content about a domain the SME covers Available SME sources: - "conduit" — Pharmaceutical compounding compliance expert (USP 795/797/800, state regulations) Routing: pharma / USP 795·797·800 / sterile·non-sterile compounding / BUD / board-of-pharmacy compliance fact you must get right → call query_sme (the verified Conduit SME) to fact-check it BEFORE escalating to a human or deriving the rule yourself; cite its sources. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
query_sme accepts 4 parameters: context, question, companyId, sme_source. Required: question, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for query_sme: 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 Freedom Mcp. Nothing to install.
query_sme 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 query_sme 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 query_sme. 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.
query_sme is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue