# Page Not Found

The URL `files/htLdKvXGJUfZwN1xmPbd` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [21. Model DoS and Resource Exhaustion](https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/chapter_21_model_dos_resource_exhaustion.md)
- [6. Scoping an Engagement](https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/chapter_06_scoping_an_engagement.md)
- [11. Plugins, Extensions, and External APIs](https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/chapter_11_plugins_extensions_and_external_apis.md)
- [20. Model Theft and Membership Inference](https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/chapter_20_model_theft_and_membership_inference.md)
- [Plugin Vulnerabilities](https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/chapter_17_01_fundamentals_and_architecture/chapter_17_03_plugin_vulnerabilities.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/chapter_21_model_dos_resource_exhaustion.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://cph-sec.gitbook.io/ai-llm-red-team-handbook-and-field-manual/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/ai-llm-red-team-handbook-and-field-manual/chapter_21_model_dos_resource_exhaustion.md`).

You may also use `Accept: text/markdown` header for content negotiation.