scan_competitor_ai_presence
Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Retu...
This record as markdown: /tools/io-github-pipeworx-io-19hz/scan-competitor-ai-presence.md
What scan_competitor_ai_presence does on 19hz
AI agents call scan_competitor_ai_presence 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 |
|---|---|---|---|
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 — only if "anthropic" is in models. Passed to api.anthropic.com per probe. |
context | string | — | Optional shared context applied to every probe (e.g. "B2B SaaS", "Boston restaurant"). Disambiguates common names. |
entities | array | Yes | Array of 2-8 entities to compare (brand/business/product names). First entry treated as the "subject" for narrative; rest are competitors. |
Parameters from the server's own tool schema.
Why scan_competitor_ai_presence is rated Low
This is purely an informational/analytical tool that retrieves and ranks data about AI visibility across competitors. It has no side effects, does not modify any state, does not execute arbitrary code, and does not delete data. The 'audit' nature is retrospective analysis only.
From the tool's definition Tool description states it 'Compare[s] AI visibility across multiple entities', 'Probes each entity', and 'Returns ranked list with score, confidence, signal density'.
Attacks that exploit this kind of access
The rule that runs scan_competitor_ai_presence 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 scan_competitor_ai_presence, this is the rule to start with:
scan_competitor_ai_presence 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 scan_competitor_ai_presence call is checked against it from then on.
Questions about scan_competitor_ai_presence
Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.
scan_competitor_ai_presence accepts 4 parameters: models, _apiKey, context, entities. Required: entities. 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 scan_competitor_ai_presence: 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.
scan_competitor_ai_presence 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 scan_competitor_ai_presence 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 scan_competitor_ai_presence. 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.
scan_competitor_ai_presence 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