Check how the 5 major AI search engines (ChatGPT, Perplexity, Gemini, Claude, Bing Copilot) describe a business. Returns visibility score 0-100 + specific fixes. Deterministic, no LLM tokens used.
AI agents call ai_visibility_check to retrieve information from Fdl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only reconnaissance tool that gathers information from external AI search engines and presents it in a deterministic scorecard format. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal: an attacker could only gather competitive intelligence about a business's AI search visibility. Classification as Read is appropriate.
From the tool's definition Tool performs a 'Check' and 'Returns visibility score...+ specific fixes' — it queries and retrieves data about how AI search engines describe a business without modifying, executing operations, or causing side effects.
Attacks that exploit this kind of access
Check how the 5 major AI search engines (ChatGPT, Perplexity, Gemini, Claude, Bing Copilot) describe a business. Returns visibility score 0-100 + specific fixes. Deterministic, no LLM tokens used. It is categorised as a Read tool in the Fdl MCP Server, which means it retrieves data without modifying state.
Register the Fdl 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 Fdl. 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 Fdl MCP server (nareshdevelop/fdl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →