Create a manual placement test to check email deliverability across different providers.
AI agents invoke smartlead_create_manual_placement_test to trigger actions in SmartLead MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — sending test emails to various providers to check deliverability. It executes an active test rather than merely reading or writing data, and its effects (sending emails) depend on the configured arguments. It is not purely destructive or financial, but it does initiate real external email delivery actions.
From the tool's definition Create a manual placement test to check email deliverability across different providers
Documented attack patterns abuse exactly the kind of access smartlead_create_manual_placement_test gives an agent:
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_create_manual_placement_test:
{
"version": "1",
"default": "deny",
"tools": {
"smartlead_create_manual_placement_test": {
"limits": [
{
"counter": "smartlead_create_manual_placement_test_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} smartlead_create_manual_placement_test stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a manual placement test to check email deliverability across different providers. It is categorised as a Execute tool in the SmartLead MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SmartLead MCP Server MCP server in PolicyLayer and add a rule for smartlead_create_manual_placement_test: 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.
smartlead_create_manual_placement_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the smartlead_create_manual_placement_test 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 smartlead_create_manual_placement_test. 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.
smartlead_create_manual_placement_test 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.
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.
Free to start. No card required.
116 SmartLead MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.