unread_count

Get number of unread messages

SERVERMIDAS Protocol SOURCEhttps://mcp.midasprotocol.org/mcp

Low RISK CLASS

Category Read

Parameters 00 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/unread-count.md

WHAT IT DOES

What unread_count does on MIDAS Protocol

AI agents call unread_count 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.

RISK

Why unread_count is rated Low

This tool only reads and returns a count of unread messages. It has no side effects, cannot modify data, execute code, delete data, or affect financial transactions. Despite being on a financial infrastructure server, this specific tool performs a pure information retrieval operation, making it a Read category with low severity and blast radius.

From the tool's definition Tool name 'unread_count' and description 'Get number of unread messages' indicate a simple query operation that retrieves message metadata without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs unread_count 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 unread_count, this is the rule to start with:

unread_count Allowed

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

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 unread_count call is checked against it from then on.

FAQ

Questions about unread_count

What does the unread_count tool do? +

Get number of unread messages. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on unread_count? +

Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for unread_count: 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 unread_count? +

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

Can I rate-limit unread_count? +

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

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

unread_count 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 →