list_campaign_replies
List sent / received emails for an outreach campaign, newest first — subject, body preview, and reply classification. Requires authentication.
This record as markdown: /tools/com-meta-council-decision-intelligence/list-campaign-replies.md
What list_campaign_replies does on Meta Council
AI agents call list_campaign_replies 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 rows (default 50, max 200). |
direction | string | — | 'inbound' (replies from prospects — the default), 'outbound' (sent), or '' for all. |
campaign_id | string | Yes | Campaign UUID (from list_outreach_campaigns). |
Parameters from the server's own tool schema.
Why list_campaign_replies is rated Low
This tool retrieves and queries existing email data from an outreach campaign. It performs a read-only operation that returns historical email metadata and classifications. There is no capability to create, modify, delete, execute code, or trigger financial transactions. The requirement for authentication is a standard security control and does not elevate the risk category.
From the tool's definition Tool name is 'list_campaign_replies' and description explicitly states it 'List[s] sent / received emails' with 'subject, body preview, and reply classification.' The verb 'list' and the retrieval-only nature (no modification, deletion, or execution…
Attacks that exploit this kind of access
The rule that runs list_campaign_replies 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 list_campaign_replies, this is the rule to start with:
list_campaign_replies 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 list_campaign_replies call is checked against it from then on.
Questions about list_campaign_replies
List sent / received emails for an outreach campaign, newest first — subject, body preview, and reply classification. Requires authentication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
list_campaign_replies accepts 3 parameters: limit, direction, campaign_id. Required: 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 list_campaign_replies: 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.
list_campaign_replies 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 list_campaign_replies 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 list_campaign_replies. 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.
list_campaign_replies 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