search_outreach_leads
Search the user's outreach leads — filter by a text query (company / contact / email), pipeline status, and/or campaign. Returns stable IDs, evidence, holds and exact rendered draft bytes/hash for review. Replies over 256 KiB refuse in full; narrow the query or limit. Requires authentication.
This record as markdown: /tools/com-meta-council-decision-intelligence/search-outreach-leads.md
What search_outreach_leads does on Meta Council
AI agents call search_outreach_leads to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max leads to return (default 20, max 100). |
search | string | — | Text to match against company / contact name / title / email. |
status | string | — | Filter by pipeline status (e.g. 'ready', 'sent', 'replied'). |
campaign_id | string | — | Filter to a single campaign id. |
Parameters from the server's own tool schema.
Why search_outreach_leads is rated Low
Even though search_outreach_leads only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_outreach_leads 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 search_outreach_leads, this is the rule to start with:
search_outreach_leads is read-only, so it stays allowed. 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 search_outreach_leads call is checked against it from then on.
Questions about search_outreach_leads
Search the user's outreach leads — filter by a text query (company / contact / email), pipeline status, and/or campaign. Returns stable IDs, evidence, holds and exact rendered draft bytes/hash for review. Replies over 256 KiB refuse in full; narrow the query or limit. Requires authentication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
search_outreach_leads accepts 4 parameters: limit, search, status, campaign_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 search_outreach_leads: 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.
search_outreach_leads is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_outreach_leads 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 search_outreach_leads. 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.
search_outreach_leads 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