custom_get_landing_page_by_id
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-get-landing-page-by-id.md
What custom_get_landing_page_by_id does on Marketo MCP Server
AI agents call custom_get_landing_page_by_id 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_landing_page_by_id is rated Low
This tool retrieves data (a landing page) by identifier with no side effects. It is a read-only query operation. Severity is low because it only accesses information without the ability to modify assets, trigger campaigns, or cause financial impact. The custom prefix and API-call nature do not elevate the risk category beyond Read.
From the tool's definition Tool name contains 'get' and description indicates it 'calls the Marketo REST API directly' to retrieve a landing page by ID. No modification, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
The rule that runs custom_get_landing_page_by_id 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_get_landing_page_by_id, this is the rule to start with:
custom_get_landing_page_by_id is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every custom_get_landing_page_by_id call is checked against it from then on.
Questions about custom_get_landing_page_by_id
[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_landing_page_by_id: 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_landing_page_by_id 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_landing_page_by_id 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_landing_page_by_id. 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_landing_page_by_id 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.
This server
Across the catalogue