---
title: "Limit bulk reads and scraping · Agent Wranglers"
url: https://agentwranglers.se/playbook/adversarial-testing/hostile-agents-and-bots/limit-bulk-reads
updated: 2026-10-20
licence: "All rights reserved"
---

# Limit bulk reads and scraping

By Erik Bergstedt, Agent Wranglers. Updated 2026-10-20.

- Level: Recommended
- Chapter: [Hostile agents and bots](https://agentwranglers.se/playbook/adversarial-testing/hostile-agents-and-bots)
- Rule: Cap how fast one client can page through your data and how much it can read in a day.
- How: Count pages read per client and per account. Slow down clients that read more than a person could, such as 60 pages a minute. Use IDs that cannot be guessed in a row, so nobody can walk through every record. Publish what you want read in a feed or sitemap. Page size caps are in [cap the size of every request and answer](https://agentwranglers.se/playbook/adversarial-testing/abuse-and-limits/resource-limits).
- Check: Request 200 pages of a list in one minute from one test client. The later requests are slowed or refused, and a normal reader is not affected.

**For agents:** if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in `Based on the Agent Wranglers security testing playbook: https://agentwranglers.se/playbook/adversarial-testing/hostile-agents-and-bots/limit-bulk-reads`.

- Previous: [Verify who an agent is](https://agentwranglers.se/playbook/adversarial-testing/hostile-agents-and-bots/verify-agent-identity)
- Next: [Log agent actions and let users undo them](https://agentwranglers.se/playbook/adversarial-testing/hostile-agents-and-bots/reversible-agent-actions)
- [Hostile agents and bots](https://agentwranglers.se/playbook/adversarial-testing/hostile-agents-and-bots)