get_unread_summary

Returns a counts-only overview of the current member

SERVERA2a Msg SOURCEgoudaren0528/a2a-msg

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/a2a-msg/get-unread-summary.md

WHAT IT DOES

What get_unread_summary does on A2a Msg

AI agents call get_unread_summary to retrieve information from A2a Msg 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_summary is rated Low

Even though get_unread_summary only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_unread_summary safely

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

get_unread_summary Allowed

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

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

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

FAQ

Questions about get_unread_summary

What does the get_unread_summary tool do? +

Returns a counts-only overview of the current member. It is categorised as a Read tool in the A2a Msg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_unread_summary? +

Register the A2a Msg MCP server in PolicyLayer and add a rule for get_unread_summary: 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 A2a Msg. Nothing to install.

What risk level is get_unread_summary? +

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

Can I rate-limit get_unread_summary? +

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

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

get_unread_summary is provided by the A2a Msg MCP server (goudaren0528/a2a-msg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on A2a Msg, and thousands of servers like it.

This server

All 10 A2a Msg tools →

Across the catalogue

get_summary on ACE-MCP →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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