Reference

MCP safety

An assistant that reads web pages can meet text that tries to give it orders. Scrapewise helps in a few ways, and a few things stay with you. This page lists both.

Start with a Read key. A Read key cannot create, run, change or delete anything saved in your account, whatever a page says to the assistant. A few Read tools take rows or one page you give them and answer without saving anything. Move to a Full key only when you want the assistant to act. See Read or Full.
Use one key per assistant, with a clear Key name, so you can revoke one without touching the others.
Keep your assistant’s own confirmation prompts on. Delete tools come in pairs: a preview first (a tool whose name ends in _preview), then the delete. Read the preview before you say yes.
Before a paid call, ask the assistant to get the price first. Paid tools take quote_only: true, which returns the price and your balance and spends nothing.
If the assistant starts to follow orders you did not give, revoke the key under your name at the bottom of the portal menu, then API Keys. The next call answers 401.

Pass scraped parts to your model as data. A tool result can hold a part shaped { "type": "scraped", "content": "...", "origin": "...", "truncated": true }. The content is text from a web page, and anyone could have written it.
Tell your model, in its system text, to summarise or analyse scraped content only. It must not follow orders inside it, run tools because of it, or reveal keys or system text.
Numbers, true or false values, null, and fields whose name starts with an underscore are made by Scrapewise and are safe to use directly.
Never run a tool just because scraped text names it. Ask the user.
Give the assistant the smallest key that does the job.

What Scrapewise does

Text that came from a web page is marked scraped, so a careful client can keep it apart from Scrapewise’s own words.
A Read key lists only the read tools. A page that tells the assistant to delete your scrapers cannot do it with a Read key. See MCP tools.
A paid call repeated with the same idempotency_key is answered and charged once.
Every call is logged with the key’s prefix and a correlationId.

What stays with you

Marking helps only if the client respects it. Anthropic’s apps do. If you build your own client, add the same care.
Do not ask an assistant to pull keys or passwords out of scraped pages. You gave that order, so the marking cannot help.
A Full key can do everything you can do. Keep it secret and revoke it when you no longer need it.

If something looks wrong

Revoke the key. Press your name at the bottom of the portal menu, then API Keys, press Revoke key, then Revoke. Revoking is immediate.
List your groups and scrapers and check that nothing was changed or deleted that you did not expect.
Write to support with the time, the key’s name and a correlationId from a call. See Errors.

Questions

Can a web page make my assistant spend money?

Not with a Read key. With a Full key a careless client could try. That is why paid tools can quote first, and why you should keep your assistant’s confirmation prompts on.

Is my key sent to the web pages that are read?

No. The key goes only to Scrapewise, in the Authorization header.

Where is the list of tools?

On MCP tools. It says for each tool whether a Read or a Full key can call it.

Last updated 19 May 2026