Retrieve full details for a specific campaign by ID. Returns all campaign fields including status, objective, budget, and timing.
AI agents call get_campaign to retrieve information from Meta Marketing API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns campaign information from Meta's advertising system. It performs no modifications, deletions, financial transactions, or code execution. The operation is a straightforward data retrieval with no side effects, fitting the Read category.
From the tool's definition Tool description states 'Retrieve full details for a specific campaign by ID' and 'Returns all campaign fields'. The verb 'Retrieve' and the read-only nature of fetching campaign data without modification.
Attacks that exploit this kind of access
Retrieve full details for a specific campaign by ID. Returns all campaign fields including status, objective, budget, and timing. It is categorised as a Read tool in the Meta Marketing API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta Marketing API MCP Server MCP server in PolicyLayer and add a rule for get_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 Marketing API MCP Server. Nothing to install.
get_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_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_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_campaign is provided by the Meta Marketing API MCP Server MCP server (pythonando/meta-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 →