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 use generate_llms_txt to create or update resources in Bhagavad Gita — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bhagavad Gita environment.
| 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.
This tool creates new data (a generated llms.txt file) that would be written to a web server's root directory. It performs a reversible modification—the file can be edited, replaced, or deleted—making it a Write operation rather than Read (which would only retrieve data) or Execute (which would run arbitrary code).
From the tool's definition Tool description states it 'emits the standard llms.txt markdown format' and produces 'Output is a single text blob ready to drop at site-root/llms.txt', indicating it generates and creates content intended to be written to a file system location.
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 Write tool in the Bhagavad Gita MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 Bhagavad Gita 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 Bhagavad Gita. Nothing to install.
generate_llms_txt is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 Bhagavad Gita MCP server (https://gateway.pipeworx.io/bhagavad-gita/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 →