AI agents invoke test_campaign to trigger actions in Moengage. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the tool name and context of a marketing platform, 'test_campaign' most likely triggers a test execution of a campaign (sending test messages/emails to recipients), which constitutes an external operation with real-world effects. This places it in the Execute category. Severity is high because misuse could trigger unintended campaign sends to real users or test lists.
From the tool's definition Tool name 'test_campaign' on a marketing platform MCP server; description is empty and uninformative.
Attacks that exploit this kind of access
test_campaign. It is categorised as a Execute tool in the Moengage MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Moengage MCP server in PolicyLayer and add a rule for test_campaign: 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 Moengage. Nothing to install.
test_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_campaign 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 test_campaign. 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.
test_campaign is provided by the Moengage MCP server (poddubnyoleg/moengage_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 →