update_outreach_lead_status

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

Medium RISK CLASS

Category Write

Parameters 61 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/update-outreach-lead-status.md

WHAT IT DOES

What update_outreach_lead_status does on Meta Council

AI agents use update_outreach_lead_status 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
`notes`	string	—	Optional free-text notes.
`status`	string	—	New pipeline status (e.g. 'ready', 'sent', 'replied', 'closed_won', 'closed_lost').
`lead_id`	string	Yes	Lead id to update (from search_outreach_leads).
`pitch_id`	string	—	Optional pitch id to attach to the lead.
`response_text`	string	—	Optional recorded reply text.
`response_type`	string	—	Optional reply classification (e.g. 'positive', 'negative', 'neutral').

Parameters from the server's own tool schema.

RISK

Why update_outreach_lead_status is rated Medium

The tool creates or modifies lead records in a CRM/pipeline context by updating status, notes, and recorded communications. These are reversible changes (status can be changed again, notes edited) with no irreversible deletion, financial transaction, or code execution. The impact is limited to data mutation within a business process workflow.

From the tool's definition update_outreach_lead_status performs 'Advance a lead through the pipeline — set its status / pipeline stage and, optionally, a recorded reply, pitch, or notes.' This modifies lead data (status, notes, recorded interactions) reversibly without deletion or code…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_outreach_lead_status Rate-limited

update_outreach_lead_status 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": {
    "update_outreach_lead_status": {
      "limits": [
        {
          "counter": "update_outreach_lead_status_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 update_outreach_lead_status call is checked against it from then on.

FAQ

Questions about update_outreach_lead_status

What does the update_outreach_lead_status tool do? +

Advance a lead through the pipeline — set its status / pipeline stage and, optionally, a recorded reply, pitch, or notes. The core pipeline-drive action. Idempotent (setting the same status twice is a no-op). 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 update_outreach_lead_status accept? +

update_outreach_lead_status accepts 6 parameters: notes, status, lead_id, pitch_id, response_text, response_type. Required: lead_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_outreach_lead_status? +

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

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

Can I rate-limit update_outreach_lead_status? +

Yes. Add a rate_limit block to the update_outreach_lead_status 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 update_outreach_lead_status completely? +

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

update_outreach_lead_status 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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