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

custom_get_email_cc_fields

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

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

This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-get-email-cc-fields.md

What custom_get_email_cc_fields does on Marketo MCP Server

AI agents call custom_get_email_cc_fields to retrieve information from Marketo MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why custom_get_email_cc_fields is rated Low

This tool retrieves email CC field information from Marketo. It performs a GET-style operation with no side effects—it queries data without creating, modifying, or deleting records. While it accesses Marketo's email configuration, the read-only nature and lack of execution or destructive capabilities place it in the Read category with low severity.

From the tool's definition The tool name 'custom_get_email_cc_fields' begins with 'get', which typically indicates data retrieval. The description states it 'Calls the Marketo REST API directly', and the context of a Marketo server dealing with email operations suggests this retrieves…

Questions about custom_get_email_cc_fields

What does the custom_get_email_cc_fields tool do? +

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Read tool in the Marketo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on custom_get_email_cc_fields? +

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

custom_get_email_cc_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit custom_get_email_cc_fields? +

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

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

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