approve_outreach_draft
Record exact draft approval bound to recipient, campaign, subject and body. Supply the reviewed draft_sha256 as expected_draft_sha256; changed input refuses. This does not create consent, enroll or send. Requires outreach:write.
This record as markdown: /tools/com-meta-council-decision-intelligence/approve-outreach-draft.md
What approve_outreach_draft does on Meta Council
AI agents use approve_outreach_draft 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 |
|---|---|---|---|
body | object | — | |
lead_id | string | Yes | |
subject | object | — | |
recipient | object | — | |
expected_draft_sha256 | string | Yes |
Parameters from the server's own tool schema.
Why approve_outreach_draft is rated Medium
An AI agent can call approve_outreach_draft faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs approve_outreach_draft 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 approve_outreach_draft, this is the rule to start with:
approve_outreach_draft 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 approve_outreach_draft call is checked against it from then on.
Questions about approve_outreach_draft
Record exact draft approval bound to recipient, campaign, subject and body. Supply the reviewed draft_sha256 as expected_draft_sha256; changed input refuses. This does not create consent, enroll or send. Requires outreach:write. 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.
approve_outreach_draft accepts 5 parameters: body, lead_id, subject, recipient, expected_draft_sha256. Required: lead_id, expected_draft_sha256. 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 approve_outreach_draft: 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.
approve_outreach_draft 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 approve_outreach_draft 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 approve_outreach_draft. 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.
approve_outreach_draft 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