postmark_list_message_streams
AI agents call postmark_list_message_streams 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 lists/enumerates message streams from Postmark (an email service provider), which is a data retrieval operation with no side effects. The 'list' verb indicates a query-only action. Despite the empty description limiting full context, the naming convention strongly indicates a Read operation with low risk of misuse. No financial, destructive, or write operations are implied by the name.
From the tool's definition Tool name 'postmark_list_message_streams' uses the verb 'list', which retrieves and enumerates data without modification. The 'list' operation pattern is a standard Read operation that queries existing message streams.
Attacks that exploit this kind of access
postmark_list_message_streams. 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_list_message_streams: 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_list_message_streams 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_list_message_streams 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_list_message_streams. 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_list_message_streams 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 →