List Mailosaur virtual security devices used for TOTP testing.
AI agents call mailosaur_devices_list to retrieve information from Mailosaur MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply retrieves and displays information about existing virtual security devices. It has no side effects, does not modify any data, and does not execute code or trigger external operations. The blast radius of misuse is minimal — an attacker could only gain visibility into what devices exist in the testing environment, which is low-impact information disclosure in a test/staging context.
From the tool's definition Tool name includes 'list' and description states 'List Mailosaur virtual security devices' — a pure retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List Mailosaur virtual security devices used for TOTP testing. It is categorised as a Read tool in the Mailosaur MCP MCP Server, which means it retrieves data without modifying state.
Register the Mailosaur MCP server in PolicyLayer and add a rule for mailosaur_devices_list: 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 Mailosaur MCP. Nothing to install.
mailosaur_devices_list 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 mailosaur_devices_list 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 mailosaur_devices_list. 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.
mailosaur_devices_list is provided by the Mailosaur MCP server (mrnewdelhi/mailosaur-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 →