get_usage

Get account usage metrics: inboxes, emails sent/received, plan limits.

SERVERPypi:deadsimple Email SOURCEpypi:deadsimple-email

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/deadsimple-email/get-usage.md

WHAT IT DOES

What get_usage does on Pypi:deadsimple Email

AI agents call get_usage to retrieve information from Pypi:deadsimple Email 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_usage is rated Low

This tool retrieves and reports account statistics and plan information. It has no side effects, does not modify data, execute code, delete resources, or affect financial operations. It is a pure read operation that aggregates metrics for informational purposes.

From the tool's definition Tool name 'get_usage' and description 'Get account usage metrics: inboxes, emails sent/received, plan limits' indicate a query operation that retrieves metrics without modifying or executing actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_usage safely

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

get_usage Allowed

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

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

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

FAQ

Questions about get_usage

What does the get_usage tool do? +

Get account usage metrics: inboxes, emails sent/received, plan limits. It is categorised as a Read tool in the Pypi:deadsimple Email MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage? +

Register the Pypi:deadsimple Email MCP server in PolicyLayer and add a rule for get_usage: 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 Pypi:deadsimple Email. Nothing to install.

What risk level is get_usage? +

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

Can I rate-limit get_usage? +

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

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

get_usage is provided by the Pypi:deadsimple Email MCP server (pypi:deadsimple-email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pypi:deadsimple Email, and thousands of servers like it.

This server

All 14 Pypi:deadsimple Email 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 →