Resend an invoice email for a previously charged transaction.
AI agents invoke resend_invoice to trigger actions in Ontraport MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external email operation (resending an invoice email), which is an external communication action. It does not delete data or move money directly, but it executes an outbound email action with real-world side effects. The blast radius is medium since misuse could cause repeated unwanted emails to customers.
From the tool's definition Resend an invoice email for a previously charged transaction
Attacks that exploit this kind of access
Resend an invoice email for a previously charged transaction. It is categorised as a Execute tool in the Ontraport MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ontraport MCP Server MCP server in PolicyLayer and add a rule for resend_invoice: 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 Ontraport MCP Server. Nothing to install.
resend_invoice is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resend_invoice 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 resend_invoice. 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.
resend_invoice is provided by the Ontraport MCP Server MCP server (landonray/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →