get_marketing_campaign
Get one owned marketing campaign with its brand, audience, channels, and dates.
This record as markdown: /tools/com-meta-council-decision-intelligence/get-marketing-campaign.md
What get_marketing_campaign does on Meta Council
AI agents call get_marketing_campaign to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
campaign_id | string | Yes | Full UUID from the matching list tool. |
Parameters from the server's own tool schema.
Why get_marketing_campaign is rated Low
This tool retrieves campaign information without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk even if misused by an AI agent, as it only exposes existing campaign data. The blast radius is confined to information disclosure of marketing campaign details.
From the tool's definition Tool name 'get_marketing_campaign' and description 'Get one owned marketing campaign' indicates retrieval of campaign metadata (brand, audience, channels, dates). The verb 'Get' and lack of modification language confirm read-only behavior.
Attacks that exploit this kind of access
The rule that runs get_marketing_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_marketing_campaign, this is the rule to start with:
get_marketing_campaign 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 Meta Council, apply this rule, and every get_marketing_campaign call is checked against it from then on.
Questions about get_marketing_campaign
Get one owned marketing campaign with its brand, audience, channels, and dates. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_marketing_campaign accepts 1 parameter: campaign_id. Required: campaign_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for get_marketing_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 Meta Council. Nothing to install.
get_marketing_campaign 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_marketing_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 get_marketing_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.
get_marketing_campaign is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue