add_outreach_lead

Add a single lead to the authenticated user's outreach book. Returns the new lead id. Provenance is stamped source="agent" server-side. Does not send any email. Requires authentication.

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 70 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/add-outreach-lead.md

WHAT IT DOES

What add_outreach_lead does on Meta Council

AI agents use add_outreach_lead 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
`email`	string	—	Optional published work email; omitted means held research.
`notes`	string	—	Optional free-text notes.
`domain`	string	—	Optional company domain.
`company`	string	—	Optional company name.
`segment`	string	—	Optional segment label.
`contact_name`	string	—	Optional contact full name.
`contact_title`	string	—	Optional contact job title.

Parameters from the server's own tool schema.

RISK

Why add_outreach_lead is rated Medium

An AI agent can call add_outreach_lead 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_outreach_lead 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 add_outreach_lead, this is the rule to start with:

add_outreach_lead Rate-limited

add_outreach_lead 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_outreach_lead": {
      "limits": [
        {
          "counter": "add_outreach_lead_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every add_outreach_lead call is checked against it from then on.

FAQ

Questions about add_outreach_lead

What does the add_outreach_lead tool do? +

Add a single lead to the authenticated user's outreach book. Returns the new lead id. Provenance is stamped source="agent" server-side. Does not send any email. 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.

What parameters does add_outreach_lead accept? +

add_outreach_lead accepts 7 parameters: email, notes, domain, company, segment, contact_name, contact_title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_outreach_lead? +

Register the Meta Council MCP server in PolicyLayer and add a rule for add_outreach_lead: 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.

What risk level is add_outreach_lead? +

add_outreach_lead is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_outreach_lead? +

Yes. Add a rate_limit block to the add_outreach_lead 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.

How do I block add_outreach_lead completely? +

Set action: deny in the PolicyLayer policy for add_outreach_lead. 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.

What MCP server provides add_outreach_lead? +

add_outreach_lead 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.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →