postmark_list_bounces

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/postmark-list-bounces.md

WHAT IT DOES

What postmark_list_bounces does on Integrations MCP

AI agents call postmark_list_bounces to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why postmark_list_bounces is rated Low

This tool retrieves or queries bounce data from an email service with no modification capability or side effects. It falls squarely into the Read category. The blast radius is minimal since listing bounces cannot cause damage—it merely exposes bounce event information. Severity is low.

From the tool's definition Tool name 'postmark_list_bounces' indicates a list operation that retrieves bounce records from Postmark email service. The 'list' prefix and 'bounces' noun identify this as a query/retrieval function. No description provided, but naming convention is clear.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs postmark_list_bounces safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For postmark_list_bounces, this is the rule to start with:

postmark_list_bounces Allowed

postmark_list_bounces is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "postmark_list_bounces": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every postmark_list_bounces call is checked against it from then on.

FAQ

Questions about postmark_list_bounces

What does the postmark_list_bounces tool do? +

postmark_list_bounces is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on postmark_list_bounces? +

Register the Integrations MCP server in PolicyLayer and add a rule for postmark_list_bounces: 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.

What risk level is postmark_list_bounces? +

postmark_list_bounces is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit postmark_list_bounces? +

Yes. Add a rate_limit block to the postmark_list_bounces 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.

How do I block postmark_list_bounces completely? +

Set action: deny in the PolicyLayer policy for postmark_list_bounces. 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.

What MCP server provides postmark_list_bounces? +

postmark_list_bounces 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.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →