Generate standardized LLMs.txt file for a given URL, which provides context about how LLMs should interact with the website.
AI agents invoke firecrawl_generate_llmstxt to trigger actions in Mcp Docs Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool actively generates a file by processing a URL, triggering an external operation (crawling/scraping a website and producing output). It is not a simple read/query — it executes a generation pipeline whose effects depend on the URL argument. Since it produces a file artifact, it goes beyond a pure read, classifying as Execute.
From the tool's definition Generate standardized LLMs.txt file for a given URL
Attacks that exploit this kind of access
Generate standardized LLMs.txt file for a given URL, which provides context about how LLMs should interact with the website. It is categorised as a Execute tool in the Mcp Docs Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Docs Server MCP server in PolicyLayer and add a rule for firecrawl_generate_llmstxt: 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 Docs Server. Nothing to install.
firecrawl_generate_llmstxt is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the firecrawl_generate_llmstxt 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 firecrawl_generate_llmstxt. 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.
firecrawl_generate_llmstxt is provided by the Mcp Docs Server MCP server (@mastra/mcp-docs-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 →