custom_query_named_accounts

[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-query-named-accounts.md

WHAT IT DOES

What custom_query_named_accounts does on Marketo MCP Server

AI agents invoke custom_query_named_accounts 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.

RISK

Why custom_query_named_accounts is rated High

This tool executes direct REST API calls to Marketo, bypassing any abstraction layer. While named 'query', direct REST API access can trigger reads, writes, or other operations depending on the arguments passed. The description explicitly notes it is not Adobe's native MCP and calls the API directly, indicating broad and potentially unrestricted access.

From the tool's definition 'Calls the Marketo REST API directly' — executes arbitrary REST API calls against Marketo; the 'custom_query' prefix and direct API invocation suggest arbitrary operation capability beyond simple reads

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs custom_query_named_accounts 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_query_named_accounts, this is the rule to start with:

custom_query_named_accounts Rate-limited

custom_query_named_accounts 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_named_accounts": {
      "limits": [
        {
          "counter": "custom_query_named_accounts_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every custom_query_named_accounts call is checked against it from then on.

FAQ

Questions about custom_query_named_accounts

What does the custom_query_named_accounts 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_named_accounts? +

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

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

Can I rate-limit custom_query_named_accounts? +

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

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

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

KEEP EXPLORING

More on Marketo MCP Server, and thousands of servers like it.

This server

All 298 Marketo MCP Server tools → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →