custom_create_activity_export_job
A execute tool on the Marketo MCP server.
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-create-activity-export-job.md
What custom_create_activity_export_job does on Marketo MCP Server
AI agents invoke custom_create_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 custom_create_activity_export_job is rated High
The tool name implies creating an export job, which is an Execute-level operation (triggering an external operation). However, the description is empty, lowering confidence. Based on the name pattern, it likely initiates a data export process in Marketo rather than simply reading data or writing records. Severity is medium given export jobs could expose bulk activity data but are typically reversible/non-destructive.
From the tool's definition Tool name 'custom_create_activity_export_job' and empty description. The name suggests creating an export job for activity data.
Attacks that exploit this kind of access
The rule that runs custom_create_activity_export_job 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 custom_create_activity_export_job, this is the rule to start with:
custom_create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every custom_create_activity_export_job call is checked against it from then on.
Questions about custom_create_activity_export_job
custom_create_activity_export_job is a execute tool on the Marketo MCP Server MCP server. 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.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_create_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.
custom_create_activity_export_job 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 custom_create_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.
Set action: deny in the PolicyLayer policy for custom_create_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.
custom_create_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.
More on Marketo MCP Server, and thousands of servers like it.
Across the catalogue