robots_txt_generator
Build a robots.txt: allow or block all, custom disallow paths, AI-crawler blocking, crawl-delay and sitemap. Runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/robots-txt-generator.md
What robots_txt_generator does on SmartTools
AI agents invoke robots_txt_generator to trigger actions in SmartTools. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
access | string | — | allow all, block all, or custom (default allow) |
locale | string | — | Language for the source_url link (default en) |
sitemap | string | — | Sitemap URL (optional) |
block_ai | boolean | — | Also block common AI crawlers (default false) |
disallow | array | — | Paths to disallow (used when access=custom) |
crawl_delay | number | string | — | Crawl-delay in seconds (optional) |
Parameters from the server's own tool schema.
Why robots_txt_generator is rated High
robots_txt_generator triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs robots_txt_generator safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For robots_txt_generator, this is the rule to start with:
robots_txt_generator stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartTools, apply this rule, and every robots_txt_generator call is checked against it from then on.
Questions about robots_txt_generator
Build a robots.txt: allow or block all, custom disallow paths, AI-crawler blocking, crawl-delay and sitemap. Runs on smart-tools.xyz. It is categorised as a Execute tool in the SmartTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
robots_txt_generator accepts 6 parameters: access, locale, sitemap, block_ai, disallow, crawl_delay. The full parameter table on this page comes from the server's own tool schema.
Register the SmartTools MCP server in PolicyLayer and add a rule for robots_txt_generator: 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 SmartTools. Nothing to install.
robots_txt_generator 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 robots_txt_generator 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 robots_txt_generator. 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.
robots_txt_generator is provided by the SmartTools MCP server (https://smart-tools.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartTools, and thousands of servers like it.
Across the catalogue