email.transactional.status
Check delivery status of a sent email by ID — last event, timestamps (Resend)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/email.transactional.status.md
What email.transactional.status does on Apibase
AI agents call email.transactional.status to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
email_id | string | Yes | Email ID returned from send_email (e.g. "d1c6e0a8-...") |
Parameters from the server's own tool schema.
Why email.transactional.status is rated Low
Queries email delivery status without modifying or executing any actions. Pure read-only retrieval.
From the tool's definition Check delivery status of a sent email by ID — last event, timestamps
Attacks that exploit this kind of access
The rule that runs email.transactional.status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email.transactional.status, this is the rule to start with:
email.transactional.status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every email.transactional.status call is checked against it from then on.
Questions about email.transactional.status
Check delivery status of a sent email by ID — last event, timestamps (Resend). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
email.transactional.status accepts 1 parameter: email_id. Required: email_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for email.transactional.status: 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 Apibase. Nothing to install.
email.transactional.status 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 email.transactional.status 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.
Set action: deny in the PolicyLayer policy for email.transactional.status. 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.
email.transactional.status is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue