[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
AI agents call custom_list_user_roles 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 or queries user role information without side effects. Listing user roles is a read-only operation that does not create, modify, delete, or execute operations. The low severity reflects minimal blast radius if misused—it would expose organizational role metadata but not enable harmful actions like activating campaigns, approving programs, or managing lead data.
From the tool's definition Tool is described as calling 'the Marketo REST API directly' to list user roles. The name contains 'list' and 'user_roles', indicating a query/retrieval operation. There is no indication of modification, deletion, or execution of external operations.
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_list_user_roles: 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_list_user_roles 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_list_user_roles 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_list_user_roles. 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_list_user_roles 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 →