custom_enqueue_activity_export_job · Marketo MCP Server MCP

WHAT IT DOES

What custom_enqueue_activity_export_job does on Marketo MCP Server

AI agents invoke custom_enqueue_activity_export_job 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.

WHY IT NEEDS A POLICY

Why custom_enqueue_activity_export_job needs a policy

Enqueueing an export job triggers an external server-side operation in Marketo (job execution), placing it in Execute. It is not a simple read/query, nor does it delete data or involve financial transactions. Severity is high because misuse could flood Marketo's API with bulk export jobs, consuming resources and potentially exposing large volumes of activity data.

From the tool's definition custom_enqueue_activity_export_job — 'enqueue' implies triggering/starting an export job on Marketo's backend; described as calling the Marketo REST API directly

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_enqueue_activity_export_job Rate-limited

custom_enqueue_activity_export_job 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": {
    "custom_enqueue_activity_export_job": {
      "limits": [
        {
          "counter": "custom_enqueue_activity_export_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Marketo MCP Server, so you can run agents against it safely.

FAQ

Questions about custom_enqueue_activity_export_job

What does the custom_enqueue_activity_export_job tool do? +

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). 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 custom_enqueue_activity_export_job? +

Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_enqueue_activity_export_job: 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 custom_enqueue_activity_export_job? +

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

Can I rate-limit custom_enqueue_activity_export_job? +

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

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

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