Check if a URL is indexable by search engines. Performs 5-layer analysis: robots.txt rules, HTTP status, meta robots, X-Robots-Tag, and canonical tag. Free preview: GET https://indexability.apimesh.xyz/preview?url=... checks HTTP status and meta robots for free
AI agents call indexability_checker to retrieve information from APIMesh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The indexability_checker retrieves and analyzes data about a URL's search engine indexability through passive inspection of robots.txt, HTTP headers, and meta tags. This is a read-only operation with no side effects, data modification, or code execution. The tool makes HTTP requests to external URLs but does not execute arbitrary code or trigger destructive actions.
From the tool's definition Tool performs analysis and queries: 'Check if a URL is indexable', 'Performs 5-layer analysis', 'checks HTTP status and meta robots'. No creation, modification, deletion, code execution, or financial operations described.
Attacks that exploit this kind of access
Check if a URL is indexable by search engines. Performs 5-layer analysis: robots.txt rules, HTTP status, meta robots, X-Robots-Tag, and canonical tag. Free preview: GET https://indexability.apimesh.xyz/preview?url=... checks HTTP status and meta robots for free. It is categorised as a Read tool in the APIMesh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the APIMesh MCP Server MCP server in PolicyLayer and add a rule for indexability_checker: 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 APIMesh MCP Server. Nothing to install.
indexability_checker 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 indexability_checker 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 indexability_checker. 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.
indexability_checker is provided by the APIMesh MCP Server MCP server (mbeato/apimesh). 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 →