custom_get_program_member_export_job_status
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-get-program-member-export-job-status.md
What custom_get_program_member_export_job_status does on Marketo MCP Server
AI agents call custom_get_program_member_export_job_status to retrieve information from Marketo MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why custom_get_program_member_export_job_status is rated Low
This tool queries the status of an existing export job without creating, modifying, deleting, or executing actions. It is a straightforward retrieval operation that returns state information about a previously initiated export. The risk of misuse is minimal—an agent cannot cause harm by checking the status of an export job.
From the tool's definition Tool name contains 'get' and 'status'; description indicates it retrieves job status from Marketo REST API. The verb 'get' and the concept of checking 'export job status' are read operations with no side effects.
Attacks that exploit this kind of access
The rule that runs custom_get_program_member_export_job_status 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_get_program_member_export_job_status, this is the rule to start with:
custom_get_program_member_export_job_status is read-only, so it stays allowed. 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_get_program_member_export_job_status call is checked against it from then on.
Questions about custom_get_program_member_export_job_status
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Read tool in the Marketo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_get_program_member_export_job_status: 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_get_program_member_export_job_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the custom_get_program_member_export_job_status 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_get_program_member_export_job_status. 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_get_program_member_export_job_status 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.
This server
Across the catalogue