View recent email send history for your wallet, including delivery status. This is FREE — no payment required. Use this to monitor deliverability, track bounces, and debug issues. Supports pagination and status filtering. Args: - wallet_address (string): Your 0x... wallet address - limit (n...
Part of the MailerAstro MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call mailerastro_get_send_history to retrieve information from MailerAstro without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though mailerastro_get_send_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
mailerastro_get_send_history:
rules:
- action: allowSee the full MailerAstro policy for all 6 tools.
Agents calling read-class tools like mailerastro_get_send_history have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
View recent email send history for your wallet, including delivery status. This is FREE — no payment required. Use this to monitor deliverability, track bounces, and debug issues. Supports pagination and status filtering. Args: - wallet_address (string): Your 0x... wallet address - limit (number): Max results per page (1-100, default: 20) - offset (number): Skip N results for pagination (default: 0) - status ('delivered' | 'bounced' | 'pending' | 'failed', optional): Filter by status - response_format ('json' | 'markdown'): Output format (default: 'json') Returns: JSON with: total, count, offset, entries[], has_more, next_offset Examples: - Get last 10 sends: wallet_address="0x...", limit=10 - Check for bounces: wallet_address="0x...", status="bounced" - Page through history: offset=20, limit=20 (page 2) Error Handling: - 404: No history found for this wallet.. It is categorised as a Read tool in the MailerAstro MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for mailerastro_get_send_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MailerAstro MCP server.
mailerastro_get_send_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mailerastro_get_send_history rule in your Intercept 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.
Set action: deny in the Intercept policy for mailerastro_get_send_history. 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.
mailerastro_get_send_history is provided by the MailerAstro MCP server (mailerastro/mailerastro-email). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept