> For the complete documentation index, see [llms.txt](https://docs.cindereth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cindereth.com/tools/approvals.md).

# Approvals

A token approval you granted months ago still lets that contract move your tokens today. Forgotten approvals are how wallets actually get drained. This tool finds yours and revokes them.

## Steps

1. Open **Approvals**. Cinder checks your tokens against the chain's known spenders, including the Uniswap routers and Permit2.
2. Each open allowance appears with the spender's name and whether it is unlimited.
3. Press **Revoke** on anything you do not actively use. Each revoke is one `approve(0)` transaction.

## What Cinder itself asks for

Sells approve the exact amount being sold, never unlimited, and v4 permissions expire within 30 minutes. After a sweep, there is nothing left over to revoke, and this page proves it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cindereth.com/tools/approvals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
