check_inbox

Check inbox for received messages

SERVERMIDAS Protocol SOURCEhttps://mcp.midasprotocol.org/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/io-github-bbrainfrance-midas-protocol/check-inbox.md

WHAT IT DOES

What check_inbox does on MIDAS Protocol

AI agents call check_inbox to retrieve information from MIDAS Protocol 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
`type`	string	—
`limit`	number	—
`unreadOnly`	boolean	—

Parameters from the server's own tool schema.

RISK

Why check_inbox is rated Low

The tool's function is to read/retrieve existing inbox messages. While the MIDAS server handles sensitive financial operations, check_inbox itself does not create, modify, delete, move money, or execute code. It is a straightforward data retrieval action.

From the tool's definition 'Check inbox for received messages' is a retrieval operation with no side effects, consistent with the Read category definition (query, fetch, retrieval).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_inbox safely

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

check_inbox Allowed

check_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": {
    "check_inbox": {}
  }
}

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

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

FAQ

Questions about check_inbox

What does the check_inbox tool do? +

Check inbox for received messages. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.

What parameters does check_inbox accept? +

check_inbox accepts 3 parameters: type, limit, unreadOnly. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_inbox? +

Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for check_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 MIDAS Protocol. Nothing to install.

What risk level is check_inbox? +

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

Can I rate-limit check_inbox? +

Yes. Add a rate_limit block to the check_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 check_inbox completely? +

Set action: deny in the PolicyLayer policy for check_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 check_inbox? +

check_inbox is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MIDAS Protocol, and thousands of servers like it.

This server

All 44 MIDAS Protocol tools →

Across the catalogue

The MCP Attack Database →

Guides

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