aipush.analysis.visibility
Test whether AI assistants (ChatGPT, Perplexity, Gemini) know about and recommend a brand — returns per-model visibility scores (AIPush)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/aipush.analysis.visibility.md
What aipush.analysis.visibility does on Apibase
AI agents call aipush.analysis.visibility to retrieve information from Apibase 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 |
|---|---|---|---|
website_domain | string | Yes | Domain to check AI visibility for (e.g. "example.com"). Tests whether AI assistants know about and recommend this brand. |
Parameters from the server's own tool schema.
Why aipush.analysis.visibility is rated Low
Queries external AI visibility data; no side effects, no data modification, read-only retrieval.
From the tool's definition Test whether AI assistants know about and recommend a brand — returns visibility scores
Attacks that exploit this kind of access
The rule that runs aipush.analysis.visibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aipush.analysis.visibility, this is the rule to start with:
aipush.analysis.visibility 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 Apibase, apply this rule, and every aipush.analysis.visibility call is checked against it from then on.
Questions about aipush.analysis.visibility
Test whether AI assistants (ChatGPT, Perplexity, Gemini) know about and recommend a brand — returns per-model visibility scores (AIPush). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
aipush.analysis.visibility accepts 1 parameter: website_domain. Required: website_domain. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for aipush.analysis.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 Apibase. Nothing to install.
aipush.analysis.visibility 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 aipush.analysis.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.
Set action: deny in the PolicyLayer policy for aipush.analysis.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.
aipush.analysis.visibility is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue