New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

custom_approve_custom_object_type

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).

SERVERMarketo MCP Server SOURCEtyron-pretorius/marketo-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about custom_approve_custom_object_type

What does the custom_approve_custom_object_type 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_approve_custom_object_type? +

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.

What risk level is custom_approve_custom_object_type? +

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

Can I rate-limit custom_approve_custom_object_type? +

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.

How do I block custom_approve_custom_object_type completely? +

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.

What MCP server provides custom_approve_custom_object_type? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Marketo MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.