Get the parsed mail headers for a sandbox message.
AI agents call get-sandbox-message-headers to retrieve information from Mcp Mailtrap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves parsed mail headers from a sandbox message, which is a read-only operation that does not create, modify, delete, or execute any external actions. The blast radius is minimal—unauthorized access could expose email metadata but cannot modify data or trigger financial/destructive actions. Sandbox context further limits risk as it operates on test data.
From the tool's definition Tool name 'get-sandbox-message-headers' and description 'Get the parsed mail headers for a sandbox message' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the parsed mail headers for a sandbox message. It is categorised as a Read tool in the Mcp Mailtrap MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for get-sandbox-message-headers: 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 Mcp Mailtrap. Nothing to install.
get-sandbox-message-headers 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 get-sandbox-message-headers 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 get-sandbox-message-headers. 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.
get-sandbox-message-headers is provided by the Mcp Mailtrap MCP server (mcp-mailtrap). 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 →