Retrieve a single bounce by ID.
AI agents call postmark_get_bounce to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about a bounce event (typically an email delivery failure) from the Postmark email service by its ID. It performs a simple data retrieval without modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only access existing bounce records, which contain historical delivery metadata.
From the tool's definition Tool name and description indicate a retrieval operation: 'Retrieve a single bounce by ID.' The verb 'Retrieve' and the operation of fetching a bounce record by identifier are characteristic of read-only data access with no side effects.
Attacks that exploit this kind of access
Retrieve a single bounce by ID. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for postmark_get_bounce: 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_get_bounce 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 postmark_get_bounce 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_get_bounce. 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_get_bounce 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 →