Verify that a Meta ad account is ready for ad creation. Checks for account access, payment method, Facebook pages, and active campaigns. Returns a setup status, recommendations, and warnings.
AI agents call verify_account_setup 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 retrieves and validates account configuration state ('account access', 'payment method', 'Facebook pages', 'active campaigns') and returns informational results ('setup status, recommendations, and warnings'). It has no side effects—no data is created, modified, deleted, or financial transactions are initiated. This is a pure read/query operation with minimal blast radius if misused.
From the tool's definition Tool 'verify_account_setup' performs checks and verification operations ('Verify', 'Checks for', 'Returns a setup status') without modifying account data. No creation, deletion, or modification of resources is described.
Attacks that exploit this kind of access
Verify that a Meta ad account is ready for ad creation. Checks for account access, payment method, Facebook pages, and active campaigns. Returns a setup status, recommendations, and warnings. 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 verify_account_setup: 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.
verify_account_setup 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 verify_account_setup 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 verify_account_setup. 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.
verify_account_setup 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 →