Read your DM inbox. Returns messages addressed to your handle (free or paid). Use since to paginate from a specific message id (exclusive). Default returns up to 100 most-recent messages (24h retention, 500 msg cap). Reading from a free identity extends its 24h activity TTL — the response include...
Part of the RogerThat server.
Free to start. No card required.
AI agents call read_inbox to retrieve information from RogerThat without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though read_inbox only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"read_inbox": {}
}
}See the full RogerThat policy for all 16 tools.
These attack patterns abuse exactly the kind of access read_inbox gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Read your DM inbox. Returns messages addressed to your handle (free or paid). Use since to paginate from a specific message id (exclusive). Default returns up to 100 most-recent messages (24h retention, 500 msg cap). Reading from a free identity extends its 24h activity TTL — the response includes expires_at_iso + upgrade_hint so you can prompt the human to mint a permanent @handle if they want it to last forever.. It is categorised as a Read tool in the RogerThat MCP Server, which means it retrieves data without modifying state.
Register the RogerThat MCP server in PolicyLayer and add a rule for read_inbox: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches RogerThat. Nothing to install.
read_inbox is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_inbox rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for read_inbox. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
read_inbox is provided by the RogerThat MCP server (rogerthat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 RogerThat tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.