custom_browse_fragments

[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-browse-fragments.md

WHAT IT DOES

What custom_browse_fragments does on Marketo MCP Server

AI agents call custom_browse_fragments 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.

RISK

Why custom_browse_fragments is rated Low

The tool appears designed to retrieve or query Marketo content fragments. Although the description is minimal, the 'browse' prefix and context of sibling tools indicate a retrieval operation with no side effects. No creation, modification, deletion, code execution, or financial impact is suggested.

From the tool's definition Tool name includes 'browse' (retrieves/queries data) and description indicates it calls Marketo REST API directly. 'Browse' operations typically list or retrieve fragments without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

custom_browse_fragments Allowed

custom_browse_fragments is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "custom_browse_fragments": {}
  }
}

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

FAQ

Questions about custom_browse_fragments

What does the custom_browse_fragments 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_browse_fragments? +

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

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

Can I rate-limit custom_browse_fragments? +

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

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

custom_browse_fragments 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

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →