run_quality_check
Evaluate content or media against your ICP persona using Gemini 3.1 Pro vision. Actually SEES images and WATCHES videos. Returns quality scores (1-10) across 6 dimensions + specific ICP feedback. Use after generating media or drafting content to validate quality before delivering to the user. [se...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/run-quality-check.md
What run_quality_check does on Freedom Mcp
AI agents invoke run_quality_check to trigger actions in Freedom Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
task | string | — | What this deliverable is for (e.g. "X post about Freedom OS launch"). Gives the ICP evaluator context. |
content | string | — | Text content to evaluate (X post copy, email draft, newsletter). Can be combined with artifact_id for text + visual evaluation. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
artifact_id | string | — | ID of a specific artifact to evaluate (from generate_image or generate_video result). If omitted, auto-finds the most recent media artifact. |
Parameters from the server's own tool schema.
Why run_quality_check is rated High
This tool executes an external AI model (Gemini 3.1 Pro) to process and analyze user-supplied media and content. While the operation itself is non-destructive and read-like in intent, it crosses the Execute threshold because it triggers a third-party service whose behavior depends on arbitrary input arguments (any image, any video, any content).
From the tool's definition Tool description states it 'SEES images and WATCHES videos' and 'Evaluate[s] content or media against your ICP persona using Gemini 3.1 Pro vision,' indicating execution of external API calls (Google Gemini) with user-provided media as inputs.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs run_quality_check 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 run_quality_check, this is the rule to start with:
run_quality_check stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 run_quality_check call is checked against it from then on.
Questions about run_quality_check
Evaluate content or media against your ICP persona using Gemini 3.1 Pro vision. Actually SEES images and WATCHES videos. Returns quality scores (1-10) across 6 dimensions + specific ICP feedback. Use after generating media or drafting content to validate quality before delivering to the user. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_quality_check accepts 4 parameters: task, content, companyId, artifact_id. Required: 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 run_quality_check: 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.
run_quality_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_quality_check 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 run_quality_check. 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.
run_quality_check 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.
Across the catalogue