custom_query_opportunities · Marketo MCP Server MCP

WHAT IT DOES

What custom_query_opportunities does on Marketo MCP Server

AI agents invoke custom_query_opportunities 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_query_opportunities needs a policy

The tool makes direct REST API calls to Marketo without any described restriction on the HTTP method or endpoint. Since it could invoke read, write, or destructive operations depending on arguments, it must be classified at the most severe plausible level. 'Directly calls the REST API' with no guardrails makes this an Execute-level risk.

From the tool's definition 'Calls the Marketo REST API directly' — arbitrary API call with no described constraints on what operations can be performed

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_query_opportunities Rate-limited

custom_query_opportunities 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_query_opportunities": {
      "limits": [
        {
          "counter": "custom_query_opportunities_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_query_opportunities

What does the custom_query_opportunities 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_query_opportunities? +

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

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

Can I rate-limit custom_query_opportunities? +

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

Set action: deny in the PolicyLayer policy for custom_query_opportunities. 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_query_opportunities? +

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