custom_transition_email_template2_state
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-transition-email-template2-state.md
What custom_transition_email_template2_state does on Marketo MCP Server
AI agents invoke custom_transition_email_template2_state 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_transition_email_template2_state is rated High
The tool executes a direct Marketo REST API call to transition an email template's state. State transitions (e.g., draft, approved, archived) can have significant downstream effects on live marketing campaigns. The description is largely uninformative beyond 'calls the REST API directly', which lowers confidence.
From the tool's definition 'Calls the Marketo REST API directly' and the name suggests a state transition on an email template, implying execution of an API operation that changes system state
Attacks that exploit this kind of access
The rule that runs custom_transition_email_template2_state 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_transition_email_template2_state, this is the rule to start with:
custom_transition_email_template2_state 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_transition_email_template2_state call is checked against it from then on.
Questions about custom_transition_email_template2_state
[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.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_transition_email_template2_state: 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_transition_email_template2_state 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_transition_email_template2_state 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_transition_email_template2_state. 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_transition_email_template2_state 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