get_unread_count

Get unread message count across all mailboxes.

SERVERIconnect SOURCEiconnect-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-heznpc-iconnect/get-unread-count.md

WHAT IT DOES

What get_unread_count does on Iconnect

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

RISK

Why get_unread_count is rated Low

This tool performs a pure read operation: querying mailbox state to retrieve the count of unread messages. It has no side effects, does not modify, delete, or execute anything, and the blast radius of misuse is minimal. The only data exposed is an aggregated count metric, which poses minimal security risk even if accessed by an unauthorized agent.

From the tool's definition The tool name 'get_unread_count' and description 'Get unread message count across all mailboxes' indicate a retrieval operation with no modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_unread_count safely

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

get_unread_count Allowed

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

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

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

FAQ

Questions about get_unread_count

What does the get_unread_count tool do? +

Get unread message count across all mailboxes. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_unread_count? +

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

What risk level is get_unread_count? +

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

Can I rate-limit get_unread_count? +

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

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

get_unread_count is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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