ai_visibility_check
Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass _apiKey to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns per-model {score, con...
This record as markdown: /tools/io-github-pipeworx-io-19hz/ai-visibility-check.md
What ai_visibility_check does on 19hz
AI agents call ai_visibility_check to retrieve information from 19hz 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 |
|---|---|---|---|
entity | string | Yes | The thing to ask about. Brand/business name, product name, person, or topic. E.g. "Pipeworx", "OpenInvoice", "Acme Corp pricing". |
models | array | — | Which models to probe. Supported: "workers-ai" (free default), "anthropic" (requires _apiKey). Omit for just workers-ai. |
_apiKey | string | — | Optional Anthropic API key (sk-ant-...) — only needed if "anthropic" is in models. Passed straight through to api.anthropic.com. |
context | string | — | Optional: a phrase locating the entity (e.g. "Boston restaurant", "B2B SaaS"). Helps disambiguate common names. |
Parameters from the server's own tool schema.
Why ai_visibility_check is rated Low
This tool queries LLMs for existing knowledge and returns analytical results (visibility scores 0-100, confidence metrics, signals). It has no side effects on data, financial impact, or system state. The optional API key parameter enables queries to additional services but remains read-only. The use cases (AI-marketing audits, brand checks, monitoring) are all informational/analytical.
From the tool's definition Tool 'probes' LLMs to query 'what they know' and 'score visibility', returning scores, confidence, signals, and raw responses. No modification, deletion, or execution of external operations—purely information retrieval from LLM models.
Attacks that exploit this kind of access
The rule that runs ai_visibility_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 19hz, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ai_visibility_check, this is the rule to start with:
ai_visibility_check 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 19hz, apply this rule, and every ai_visibility_check call is checked against it from then on.
Questions about ai_visibility_check
Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass _apiKey to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns per-model {score, confidence, signals, raw_response} + a combined view. Useful for AI-marketing audits, pre-launch brand checks, competitive monitoring. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.
ai_visibility_check accepts 4 parameters: entity, models, _apiKey, context. Required: entity. The full parameter table on this page comes from the server's own tool schema.
Register the 19hz MCP server in PolicyLayer and add a rule for ai_visibility_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 19hz. Nothing to install.
ai_visibility_check 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 ai_visibility_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 ai_visibility_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.
ai_visibility_check is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 19hz, and thousands of servers like it.
This server
Across the catalogue