[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
AI agents call custom_get_custom_activity_types to retrieve information from Marketo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves custom activity type definitions from Marketo without modifying, deleting, or executing operations. It is a read-only query of configuration data. The low severity reflects minimal blast radius—querying activity types poses no direct risk even if misused by an AI agent.
From the tool's definition Tool name contains 'get' and description indicates it 'calls the Marketo REST API directly' to retrieve custom activity types. The 'get' operation and absence of modification, deletion, or execution language indicate data retrieval.
Attacks that exploit this kind of access
[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.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_get_custom_activity_types: 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.
custom_get_custom_activity_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the custom_get_custom_activity_types 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.
Set action: deny in the PolicyLayer policy for custom_get_custom_activity_types. 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.
custom_get_custom_activity_types 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →