audit_brand_visibility

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

High RISK CLASS

Category Execute

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/audit-brand-visibility.md

WHAT IT DOES

What audit_brand_visibility does on Freedom Mcp

AI agents invoke audit_brand_visibility 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
`prompt`	string	Yes	A search-style query to test (e.g., "What is the best AI operating system for solopreneurs?")
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`providers`	array	Yes	Which AI search engines to audit. Options: anthropic (Claude), xai (Grok), google (Gemini), perplexity (Sonar Pro with live search)
`max_tokens`	number	—	Maximum response length per provider (default: 1000)
`temperature`	number	—	Response variability 0-1 (default: 0.7)

Parameters from the server's own tool schema.

RISK

Why audit_brand_visibility is rated High

Triggers external API calls to multiple LLMs, executing outbound operations with side effects.

From the tool's definition Sends a search query to external LLMs, checks each response

Attacks that exploit this kind of access

RECOMMENDED RULE

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

audit_brand_visibility Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "audit_brand_visibility": {
      "limits": [
        {
          "counter": "audit_brand_visibility_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about audit_brand_visibility

What does the audit_brand_visibility tool do? +

Audit whether Freedom OS appears in AI-generated search results. Sends a search query to external LLMs (Claude, Grok, Gemini, Perplexity) and checks each response for brand mentions. This is a competitive SEO/GEO auditing tool — like a mystery shopper for AI search engines. It does NOT answer questions or delegate work. 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.

What parameters does audit_brand_visibility accept? +

audit_brand_visibility accepts 5 parameters: prompt, companyId, providers, max_tokens, temperature. Required: prompt, companyId, providers. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on audit_brand_visibility? +

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

What risk level is audit_brand_visibility? +

audit_brand_visibility is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit audit_brand_visibility? +

Yes. Add a rate_limit block to the audit_brand_visibility 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 audit_brand_visibility completely? +

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

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

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →