Release a provisioned email address. Pass the id returned from
AI agents call release_email_address to permanently remove resources in Agentline — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Releasing a provisioned email address destroys the resource and cannot be undone. Any emails, 2FA codes, or ongoing communications tied to that address would be lost. This matches the Destructive category as the action is irreversible and could cause significant disruption if misused by an AI agent.
From the tool's definition 'Release a provisioned email address' — releasing/deprovisioning a resource is an irreversible action that permanently removes the email address allocation
Attacks that exploit this kind of access
Release a provisioned email address. Pass the id returned from. It is categorised as a Destructive tool in the Agentline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agentline MCP server in PolicyLayer and add a rule for release_email_address: 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 Agentline. Nothing to install.
release_email_address 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 release_email_address 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 release_email_address. 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.
release_email_address is provided by the Agentline MCP server (jgottlieb84/agentline-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 →