custom_rename_email_module

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

SERVERMarketo MCP Server SOURCEtyron-pretorius/marketo-mcp

Medium RISK CLASS

Category Write

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-rename-email-module.md

WHAT IT DOES

What custom_rename_email_module does on Marketo MCP Server

AI agents use custom_rename_email_module to create or update resources in Marketo MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Marketo MCP Server environment.

RISK

Why custom_rename_email_module is rated Medium

Renaming an email module is a create/modify operation (Write category), not destructive. However, it affects marketing assets in a production Marketo environment. The severity is high because misconfiguration or agent misuse could corrupt email module naming conventions, breaking email campaign references, though the effect is reversible.

From the tool's definition Tool description states it 'Calls the Marketo REST API directly' and the name 'custom_rename_email_module' indicates it modifies (renames) an email module. Renaming is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

custom_rename_email_module Rate-limited

custom_rename_email_module stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_rename_email_module": {
      "limits": [
        {
          "counter": "custom_rename_email_module_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_rename_email_module call is checked against it from then on.

FAQ

Questions about custom_rename_email_module

What does the custom_rename_email_module tool do? +

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Write tool in the Marketo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on custom_rename_email_module? +

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

custom_rename_email_module is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit custom_rename_email_module? +

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

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

custom_rename_email_module 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 →

Across the catalogue

forward-email on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →