Get a smart campaign by its ID from Marketo.
AI agents call get_smart_campaign_by_id 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 metadata or configuration of a smart campaign identified by ID. It is a read-only query operation that does not modify data, execute the campaign, or trigger any side effects. The verb 'Get' and the absence of any action language (activate, execute, delete, update) confirm this is a Read category tool with low severity.
From the tool's definition Tool name 'get_smart_campaign_by_id' and description 'Get a smart campaign by its ID from Marketo' indicate a retrieval operation with no modification or execution of the campaign itself.
Attacks that exploit this kind of access
Get a smart campaign by its ID from Marketo. 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 get_smart_campaign_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.
get_smart_campaign_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 get_smart_campaign_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 get_smart_campaign_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.
get_smart_campaign_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.
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 →