postmark_send_email
AI agents use postmark_send_email to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Sending emails is a Write operation that creates/modifies data (new email records in the email service and recipient inboxes) with reversible consequences (emails can theoretically be recalled or deleted, though practical recourse is limited). It is not Destructive since emails are not permanently unrecoverable by design. It is not Financial, Execute, or Read.
From the tool's definition Tool name is 'postmark_send_email', which sends emails through the Postmark email service provider. The function is to create and transmit email messages.
Attacks that exploit this kind of access
postmark_send_email. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for postmark_send_email: 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 Integrations MCP. Nothing to install.
postmark_send_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the postmark_send_email 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 postmark_send_email. 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.
postmark_send_email is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →