request_campaign

Request a smart campaign for specific leads.

SERVERMarketo MCP Server SOURCEtyron-pretorius/marketo-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tyron-pretorius-marketo-mcp/request-campaign.md

WHAT IT DOES

What request_campaign does on Marketo MCP Server

AI agents invoke request_campaign to trigger actions in Marketo 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.

RISK

Why request_campaign is rated High

Requesting a smart campaign causes Marketo to execute automated marketing workflows (emails, data changes, scoring, etc.) against specific leads. This is an external operation trigger whose effects depend on arguments (which campaign, which leads). Effects may include sending emails, changing lead data, or enrolling leads in nurture tracks — not purely a write or read action, but execution of a campaign pipeline.

From the tool's definition 'Request a smart campaign for specific leads' — triggers execution of a smart campaign against targeted lead records

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs request_campaign safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Marketo MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For request_campaign, this is the rule to start with:

request_campaign Rate-limited

request_campaign 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_campaign": {
      "limits": [
        {
          "counter": "request_campaign_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every request_campaign call is checked against it from then on.

FAQ

Questions about request_campaign

What does the request_campaign tool do? +

Request a smart campaign for specific leads. It is categorised as a Execute tool in the Marketo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on request_campaign? +

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

What risk level is request_campaign? +

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

Can I rate-limit request_campaign? +

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

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

request_campaign is provided by the Marketo MCP Server MCP server (tyron-pretorius/marketo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Marketo MCP Server, and thousands of servers like it.

This server

All 298 Marketo MCP Server tools → High-risk tools on this server →

Across the catalogue

http_request on 0sec → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →