AI agents call get_campaign_meta to retrieve information from Moengage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a metadata retrieval operation without side effects. However, confidence is medium (0.75) rather than high because the description is empty, leaving some ambiguity about the exact scope and sensitivity of the data returned. In a marketing platform context, campaign metadata could include targeting information, audience segments, or scheduling details that might be considered sensitive.
From the tool's definition Tool name 'get_campaign_meta' suggests retrieval of campaign metadata. Sibling tools include 'get_campaign_stats' and 'get_server_info', which are clearly read-only retrieval operations, positioning this tool in the Read category.
Attacks that exploit this kind of access
get_campaign_meta. It is categorised as a Read tool in the Moengage MCP Server, which means it retrieves data without modifying state.
Register the Moengage MCP server in PolicyLayer and add a rule for get_campaign_meta: 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.
get_campaign_meta 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_meta 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_meta. 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_meta 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 →