permanently archive contact in mailmodo
AI agents call archiveContact to permanently remove resources in Mailmodo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Archiving a contact permanently is a destructive operation because it irreversibly alters the state of contact data. While not a hard deletion, permanent archival prevents normal access and use of the contact record, effectively removing it from active management. This is more severe than a reversible Write action.
From the tool's definition Tool description states 'permanently archive contact in mailmodo' — the word 'permanently' indicates an irreversible action that removes or hides contact data from normal operations.
Attacks that exploit this kind of access
permanently archive contact in mailmodo. It is categorised as a Destructive tool in the Mailmodo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mailmodo MCP server in PolicyLayer and add a rule for archiveContact: 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 Mailmodo. Nothing to install.
archiveContact is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the archiveContact 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 archiveContact. 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.
archiveContact is provided by the Mailmodo MCP server (mailmodo/mailmodo-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 →