Stop an active automated test before its end date.
AI agents invoke smartlead_stop_automated_test to trigger actions in Smartlead Simplified 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 halts an ongoing automated process early. It's an operational action that triggers an external state change (stopping a test), but it's not clearly irreversible (the test could potentially be restarted) and doesn't delete data. It falls under Execute as it triggers an external operation with side effects dependent on the target test.
From the tool's definition Stop an active automated test before its end date.
Documented attack patterns abuse exactly the kind of access smartlead_stop_automated_test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Smartlead Simplified MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smartlead_stop_automated_test:
{
"version": "1",
"default": "deny",
"tools": {
"smartlead_stop_automated_test": {
"limits": [
{
"counter": "smartlead_stop_automated_test_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} smartlead_stop_automated_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.
Stop an active automated test before its end date. It is categorised as a Execute tool in the Smartlead Simplified MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Smartlead Simplified MCP Server MCP server in PolicyLayer and add a rule for smartlead_stop_automated_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 Simplified MCP Server. Nothing to install.
smartlead_stop_automated_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_stop_automated_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_stop_automated_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_stop_automated_test is provided by the Smartlead Simplified MCP Server MCP server (jonathan-politzki/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 Simplified 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.
78 Smartlead Simplified MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.