custom_describe_custom_object_type
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-describe-custom-object-type.md
What custom_describe_custom_object_type does on Marketo MCP Server
AI agents call custom_describe_custom_object_type 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_describe_custom_object_type is rated Low
This tool retrieves schema or metadata for custom object types in Marketo. It is a read-only query operation that has no side effects—it does not create, modify, delete, or execute any changes to data or systems. The use of 'describe' combined with the Marketo context (asset management platform) indicates introspection/information retrieval, placing it firmly in the Read category with low severity.
From the tool's definition Tool name contains 'describe' and description indicates it 'Calls the Marketo REST API directly' to retrieve custom object type metadata/schema information.
Attacks that exploit this kind of access
The rule that runs custom_describe_custom_object_type 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_describe_custom_object_type, this is the rule to start with:
custom_describe_custom_object_type 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_describe_custom_object_type call is checked against it from then on.
Questions about custom_describe_custom_object_type
[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_describe_custom_object_type: 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_describe_custom_object_type 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_describe_custom_object_type 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_describe_custom_object_type. 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_describe_custom_object_type 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