custom_approve_custom_object_type
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-approve-custom-object-type.md
What custom_approve_custom_object_type does on Marketo MCP Server
AI agents invoke custom_approve_custom_object_type 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_approve_custom_object_type is rated High
The tool calls the Marketo REST API directly to approve a custom object type. Approving a custom object type is a state-change action that modifies configuration in Marketo (transitioning a draft object type to approved/live state). This makes it a Write or Execute action.
From the tool's definition 'Calls the Marketo REST API directly' and 'approve_custom_object_type' in the name
Attacks that exploit this kind of access
The rule that runs custom_approve_custom_object_type 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_approve_custom_object_type, this is the rule to start with:
custom_approve_custom_object_type 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_approve_custom_object_type call is checked against it from then on.
Questions about custom_approve_custom_object_type
[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_approve_custom_object_type: 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_approve_custom_object_type 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_approve_custom_object_type 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_approve_custom_object_type. 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_approve_custom_object_type 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