Documentation for receiving emails in an Autodock environment. Each environment can receive emails at *@{slug}.autodock.io. Emails are delivered via HTTPS webhook (SES -> Vercel -> your environment) with Bearer token authentication. A boilerplate email handler is pre-installed at /opt/autodock/...
Part of the Autodock MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke env.email to trigger processes or run actions in Autodock. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
env.email can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
env.email:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Autodock policy for all 27 tools.
Agents calling execute-class tools like env.email have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
env.email is one of the high-risk operations in Autodock. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Documentation for receiving emails in an Autodock environment. Each environment can receive emails at *@{slug}.autodock.io. Emails are delivered via HTTPS webhook (SES -> Vercel -> your environment) with Bearer token authentication. A boilerplate email handler is pre-installed at /opt/autodock/email-server.js that you can customize or replace with your own implementation. To receive emails: 1. Start the boilerplate: node /opt/autodock/email-server.js (or write your own on port 47982) 2. Handle POST /email with JSON body and validate Bearer token 3. Send emails to any address @{slug}.autodock.io WEBHOOK PAYLOAD: { from, to, subject, textBody, htmlBody, messageId, timestamp, spamVerdict, virusVerdict } LIMITS: 150KB max email (SES SNS limit). Large emails/attachments are truncated. AUTH: Bearer token (from /opt/autodock/email-webhook-secret) is required for webhook requests. If no application is listening on 47982, emails are silently dropped.. It is categorised as a Execute tool in the Autodock MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for env.email. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Autodock MCP server.
env.email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the env.email rule in your Intercept 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 Intercept policy for env.email. 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.
env.email is provided by the Autodock MCP server (mikesol/autodock). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept