Let eve operate email through the public boundary. No internal shortcut to customer data or sends.
Run internal research and operations through the same public MCP contract customers use, with a real principal, project scope, and product-enforced safeguards.
✓Internal placement changes the workflow, not the agent's authority.
Start with a read-only task
Operator prompt
Inspect the onboarding flow, explain where contacts stop, and show the evidence before proposing a change.
Connect
Remote MCP
Prompt
Inspect the live system
Boundary
Show before changing
[ 01 / 03 ]Internal operation
Preserve the public contract inside an internal workflow.
Gather evidence through tools
Inspect projects, messages, flow runs, and metrics through public operations instead of privileged database reads.
Prepare work in the product
Produce rendered template versions and paused flows with identifiers another step can review.
Keep customer-visible changes explicit
Being an internal workflow never grants approval or bypasses confirmation, kill switches, or caps.
[ 02 / 03 ]Connect
Start Eve with a task you can verify.
Connect eve through the public MCP boundary, bind it to the intended project, and verify a read-only result before scheduling any recurring work.
Verify the connection and returned evidence before delegating a change.
Inspect the live email programme for the selected company.
List the sending connection, published templates, enabled flows,
and seven-day delivery state. Do not change anything.[ 03 / 03 ]Related
Build around eve
Questions people ask us
Keep eve inside the same public boundary.
Scope an agent principal, start with evidence gathering, and preserve every returned identifier.