check_api_v23_compliance

Check if your creative parameters are compliant with Meta Marketing API v23.0 requirements. Identifies deprecated features and recommends v23.0 best practices.

Server Meta Marketing API MCP Server pythonando/meta-mcp
Category Read
Risk class Low
Parameters 00 required

What check_api_v23_compliance does on Meta Marketing API MCP Server

AI agents call check_api_v23_compliance 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.

Why check_api_v23_compliance needs a policy

This tool retrieves and analyzes compliance status against Meta API v23.0 requirements. It produces informative output (compliance status, deprecated features, recommendations) without modifying any advertising data, campaigns, creatives, or account settings. No side effects occur from running this tool.

From the tool's definition Tool performs compliance checking and identification of deprecated features with recommendations. The verb "check" and description "identifies deprecated features and recommends" indicate read-only analysis with no modifications, deletions, or external…

Questions about check_api_v23_compliance

What does the check_api_v23_compliance tool do? +

Check if your creative parameters are compliant with Meta Marketing API v23.0 requirements. Identifies deprecated features and recommends v23.0 best practices. It is categorised as a Read tool in the Meta Marketing API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_api_v23_compliance? +

Register the Meta Marketing API MCP Server MCP server in PolicyLayer and add a rule for check_api_v23_compliance: 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.

What risk level is check_api_v23_compliance? +

check_api_v23_compliance is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_api_v23_compliance? +

Yes. Add a rate_limit block to the check_api_v23_compliance 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.

How do I block check_api_v23_compliance completely? +

Set action: deny in the PolicyLayer policy for check_api_v23_compliance. 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.

What MCP server provides check_api_v23_compliance? +

check_api_v23_compliance 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.