High Risk →

start_campaign

Start a campaign to begin dialing contacts. Works on campaigns in draft or paused status. For paused campaigns, this resumes from where it left off. The campaign enters processing state and begins making calls asynchronously.

Part of the Smallest MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke start_campaign to trigger processes or run actions in Smallest. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

start_campaign can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

smallest.yaml
tools:
  start_campaign:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Smallest policy for all 70 tools.

Tool Name start_campaign
Category Execute
MCP Server Smallest MCP Server
Risk Level High

View all 70 tools →

Agents calling execute-class tools like start_campaign have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

start_campaign is one of the high-risk operations in Smallest. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the start_campaign tool do? +

Start a campaign to begin dialing contacts. Works on campaigns in draft or paused status. For paused campaigns, this resumes from where it left off. The campaign enters processing state and begins making calls asynchronously.. It is categorised as a Execute tool in the Smallest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_campaign? +

Add a rule in your Intercept YAML policy under the tools section for start_campaign. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Smallest MCP server.

What risk level is start_campaign? +

start_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_campaign? +

Yes. Add a rate_limit block to the start_campaign rule in your Intercept 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 start_campaign completely? +

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

start_campaign is provided by the Smallest MCP server (@developer-smallestai/smallest-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.