read_inbox

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/read-inbox.md

WHAT IT DOES

What read_inbox does on Mcp Server

AI agents call read_inbox to retrieve information from Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`days`	integer	—	Days back (default 14)
`peek`	boolean	—	true = do not mark read
`include_read`	boolean	—	true = re-read read and unread notes, marks nothing

Parameters from the server's own tool schema.

RISK

Why read_inbox is rated Low

Tool retrieves messages without modifying underlying data or executing operations; read operation is reversible with include_read flag.

From the tool's definition reads DC Hub inbox notes; marks read; non-destructive retrieval

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_inbox safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_inbox, this is the rule to start with:

read_inbox Allowed

read_inbox is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_inbox": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every read_inbox call is checked against it from then on.

FAQ

Questions about read_inbox

What does the read_inbox tool do? +

Use this when a partner key reads its DC Hub inbox. PARTNER KEY ONLY: notes DC Hub left for the partner agent whose key this session sends, newest first. The first read CONSUMES them (marks read), so a later session sees none; include_read=true re-reads read and unread notes (last 14 days) without marking. Non-partner key: 403. Not a data tool. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does read_inbox accept? +

read_inbox accepts 3 parameters: days, peek, include_read. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on read_inbox? +

Register the Mcp Server 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 Mcp Server. Nothing to install.

What risk level is read_inbox? +

read_inbox is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_inbox? +

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.

How do I block read_inbox completely? +

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.

What MCP server provides read_inbox? +

read_inbox is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Server, and thousands of servers like it.

This server

All 94 Mcp Server tools →

Across the catalogue

binary_read on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →