Check if a campaign is ready for ad set creation and identify potential issues
AI agents call diagnose_campaign_readiness 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 performs a read/diagnostic operation, checking the state of a campaign and reporting potential issues. It does not create, modify, delete, or execute any changes. Similar to 'check_campaign_readiness' sibling tool, it retrieves information to assess readiness without side effects.
From the tool's definition 'Check if a campaign is ready for ad set creation and identify potential issues' — purely diagnostic/read operation that retrieves and evaluates campaign status
Attacks that exploit this kind of access
Check if a campaign is ready for ad set creation and identify potential issues. 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 diagnose_campaign_readiness: 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.
diagnose_campaign_readiness 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 diagnose_campaign_readiness 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 diagnose_campaign_readiness. 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.
diagnose_campaign_readiness 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 →