get_campaign_node_run_counts
Map of workflow node ID → execution count. Useful for funnel visualization.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/get-campaign-node-run-counts.md
What get_campaign_node_run_counts does on Max MCP Server
AI agents call get_campaign_node_run_counts to retrieve information from Max 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 get_campaign_node_run_counts is rated Low
This tool retrieves metrics about workflow execution counts—purely a data lookup operation with no capacity to modify, delete, or execute operations. The blast radius of misuse is minimal; an agent could only access execution statistics, which poses negligible risk.
From the tool's definition Tool name 'get_campaign_node_run_counts' and description 'Map of workflow node ID → execution count. Useful for funnel visualization' indicate data retrieval only. The verb 'get' and read-only use case (funnel visualization/reporting) confirm no side effects.
Attacks that exploit this kind of access
The rule that runs get_campaign_node_run_counts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_campaign_node_run_counts, this is the rule to start with:
get_campaign_node_run_counts 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 Max MCP Server, apply this rule, and every get_campaign_node_run_counts call is checked against it from then on.
Questions about get_campaign_node_run_counts
Map of workflow node ID → execution count. Useful for funnel visualization. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for get_campaign_node_run_counts: 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 Max MCP Server. Nothing to install.
get_campaign_node_run_counts 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_campaign_node_run_counts 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_campaign_node_run_counts. 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_campaign_node_run_counts is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue