postmark_get_stats
AI agents call postmark_get_stats 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.
The 'get_' prefix and context of Postmark (email service) indicate this retrieves statistics/metrics without modifying data or triggering side effects. This is a read-only query operation. Severity is low as stats access poses minimal risk unless they contain highly sensitive business metrics, but Postmark stats are typically operational monitoring data.
From the tool's definition Tool name 'postmark_get_stats' with 'get' prefix indicates data retrieval. Postmark is an email service provider; 'stats' refers to querying email delivery metrics, open rates, and performance data. No description provided, lowering confidence slightly.
Attacks that exploit this kind of access
postmark_get_stats. 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_stats: 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_stats 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_stats 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_stats. 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_stats 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 →