# Limits

> What a workspace may hold and do, and what happens at a limit.

Going over a limit never loses anything. Your tables stay as they are, and you can still read, query, restore and delete: only new writes are turned down, with an error that says why. The **Activity** page of the app shows where you are.

## What a workspace may hold

| | Limit |
|---|---|
| Tables | 50, not counting the trash |
| Storage | 1 GB, counting every version and the trash |
| MCP tool calls | 2,000 a month |

The limit on tool calls counts agents' calls over MCP, and turns down writes once it's reached, until the next month. To raise a limit, write to [contact@rho.store](mailto:contact@rho.store).

## Rate limits

When a request goes over one of these, it's answered with `429` and how long to wait, in the `Retry-After` header. An MCP tool answers with a `rate_limited` error that says the same.

| | Limit |
|---|---|
| MCP tool calls | 120 a minute, per user |
| File uploads | 60 an hour, per address |
| Other API requests, including table APIs | 600 a minute, per address |