get_mailbox_stats

Get mailbox statistics

SERVERCowork Bench SOURCE0717376/cowork_bench

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/cowork-bench/get-mailbox-stats.md

WHAT IT DOES

What get_mailbox_stats does on Cowork Bench

AI agents call get_mailbox_stats to retrieve information from Cowork Bench 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_mailbox_stats is rated Low

This tool retrieves mailbox metadata/statistics without modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing data. The low severity reflects minimal blast radius—an AI agent misusing this tool would only be able to view mailbox statistics, not alter data or trigger external actions.

From the tool's definition Tool name 'get_mailbox_stats' and description 'Get mailbox statistics' indicate retrieval of statistical information from a mailbox. The verb 'get' and the focus on 'statistics' (read-only data) confirm this is a query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_mailbox_stats safely

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

get_mailbox_stats Allowed

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

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

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

FAQ

Questions about get_mailbox_stats

What does the get_mailbox_stats tool do? +

Get mailbox statistics. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_mailbox_stats? +

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

What risk level is get_mailbox_stats? +

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

Can I rate-limit get_mailbox_stats? +

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

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

get_mailbox_stats is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench 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 →