custom_sync_custom_object_type · Marketo MCP Server MCP

WHAT IT DOES

What custom_sync_custom_object_type does on Marketo MCP Server

AI agents invoke custom_sync_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 IT NEEDS A POLICY

Why custom_sync_custom_object_type needs a policy

The tool calls the Marketo REST API directly for syncing a custom object type, which implies creating or updating data in Marketo. 'Sync' operations are typically Write-level, but direct arbitrary REST API access elevates this to Execute since the full scope of what can be triggered is unclear. The description is minimal and uninformative beyond the direct API call nature, reducing confidence.

From the tool's definition 'Calls the Marketo REST API directly' and 'sync_custom_object_type' — sync operations typically create or update records, and direct REST API calls can have broad side effects

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_sync_custom_object_type Rate-limited

custom_sync_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "custom_sync_custom_object_type": {
      "limits": [
        {
          "counter": "custom_sync_custom_object_type_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Marketo MCP Server, so you can run agents against it safely.

FAQ

Questions about custom_sync_custom_object_type

What does the custom_sync_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_sync_custom_object_type? +

Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_sync_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_sync_custom_object_type? +

custom_sync_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_sync_custom_object_type? +

Yes. Add a rate_limit block to the custom_sync_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_sync_custom_object_type completely? +

Set action: deny in the PolicyLayer policy for custom_sync_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_sync_custom_object_type? +

custom_sync_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.