draft_outreach_email
Save a draft email subject and/or body onto one of the user's leads. This only stores the draft for human review — it does NOT send anything. A human sends from the dashboard. Requires authentication.
This record as markdown: /tools/com-meta-council-decision-intelligence/draft-outreach-email.md
What draft_outreach_email does on Meta Council
AI agents use draft_outreach_email to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
lead_id | string | Yes | Lead id to draft for (from search_outreach_leads). |
email_body | string | — | Draft email body. |
subject_line | string | — | Draft subject line. |
Parameters from the server's own tool schema.
Why draft_outreach_email is rated Medium
The tool creates or modifies draft email data (subject/body) associated with leads, which is reversible and has no side effects beyond storing text for human review. It does not execute sending, execute external operations, or perform destructive actions. The explicit non-sending clause and requirement for manual human action from the dashboard confirms this is Write-category only.
From the tool's definition Tool description states it 'Save[s] a draft email subject and/or body' and explicitly clarifies 'it does NOT send anything. A human sends from the dashboard.' This is data creation/modification without execution or irreversible effects.
Attacks that exploit this kind of access
The rule that runs draft_outreach_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For draft_outreach_email, this is the rule to start with:
draft_outreach_email stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every draft_outreach_email call is checked against it from then on.
Questions about draft_outreach_email
Save a draft email subject and/or body onto one of the user's leads. This only stores the draft for human review — it does NOT send anything. A human sends from the dashboard. Requires authentication. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
draft_outreach_email accepts 3 parameters: lead_id, email_body, subject_line. Required: lead_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for draft_outreach_email: 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 Meta Council. Nothing to install.
draft_outreach_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the draft_outreach_email 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 draft_outreach_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.
draft_outreach_email is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue