smartlead_fetch_lead_message_history

THE RISK

Low Risk

Why smartlead_fetch_lead_message_history needs a policy

This tool retrieves historical message data for a lead in a campaign. It has no side effects: it does not create, modify, delete, or execute anything. The blast radius of misuse is minimal — an agent could retrieve message history it shouldn't access, but no data would be altered or operations triggered. Classification as Read is appropriate.

From the tool's definition Tool name contains 'fetch' and description states 'Retrieve the complete message history' — these are unambiguous read operations that query existing data without modification, deletion, or execution.

Documented attack patterns abuse exactly the kind of access smartlead_fetch_lead_message_history gives an agent:

POLICY

How to control smartlead_fetch_lead_message_history

PolicyLayer is an MCP gateway — it sits between your AI agents and SmartLead MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smartlead_fetch_lead_message_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "smartlead_fetch_lead_message_history": {}
  }
}

smartlead_fetch_lead_message_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register SmartLead MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SmartLead MCP Server tools

Financial smartlead_place_order_for_mailboxes Place an order for specific mailboxes with a vendor. Destructive smartlead_delete_campaign Permanently delete a campaign and all associated data. This action cannot be undone. Destructive smartlead_delete_campaign_webhook Delete a specific webhook from a campaign. Destructive smartlead_delete_client_api_key Delete a specific API key. Destructive smartlead_delete_folder Delete a smart delivery folder by ID. Destructive smartlead_delete_lead_by_campaign Remove a lead from a specific campaign permanently. Destructive smartlead_delete_tests_in_bulk Delete multiple smart delivery tests at once for cleanup purposes. Destructive smartlead_remove_email_account_from_campaign Remove an email account from a specific campaign.

All 116 SmartLead MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about smartlead_fetch_lead_message_history

What does the smartlead_fetch_lead_message_history tool do? +

Retrieve the complete message history for a lead within a specific campaign. It is categorised as a Read tool in the SmartLead MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on smartlead_fetch_lead_message_history? +

Register the SmartLead MCP Server MCP server in PolicyLayer and add a rule for smartlead_fetch_lead_message_history: 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 SmartLead MCP Server. Nothing to install.

What risk level is smartlead_fetch_lead_message_history? +

smartlead_fetch_lead_message_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit smartlead_fetch_lead_message_history? +

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

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

smartlead_fetch_lead_message_history is provided by the SmartLead MCP Server MCP server (leadmagic/smartlead-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SmartLead MCP Server tool call.

Start from SmartLead MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →