Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt....
AI agents call generate_llms_txt to retrieve information from Mcp Horoscope without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Full URL of the site to summarize, e.g. "https://example.com" or a specific landing page. |
max_links | number | — | Maximum number of link entries to include (default 25, max 50). |
Parameters from the server's own tool schema.
The tool fetches and reads a remote URL, extracting metadata and links, then generates a text output. It does not write, execute, or delete anything itself — the output is a text blob the user must manually deploy. However, it does fetch arbitrary URLs (potential SSRF vector) and could be used to scrape competitor sites, warranting medium severity.
From the tool's definition Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt.
Risk signalsAccepts URL/endpoint input (url) · Admin/system-level operation
Attacks that exploit this kind of access
Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor. It is categorised as a Read tool in the Mcp Horoscope MCP Server, which means it retrieves data without modifying state.
generate_llms_txt accepts 2 parameters: url, max_links. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Horoscope MCP server in PolicyLayer and add a rule for generate_llms_txt: 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 Mcp Horoscope. Nothing to install.
generate_llms_txt 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 generate_llms_txt 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 generate_llms_txt. 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.
generate_llms_txt is provided by the Mcp Horoscope MCP server (https://gateway.pipeworx.io/horoscope/mcp). 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 →