Fetch aggregated catalog issues (rejected items, missing fields, image problems) from Meta
AI agents call get_catalog_diagnostics to retrieve information from Claude Meta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries existing catalog diagnostic data from Meta's systems. There are no side effects, no data modification, and no irreversible actions. The tool simply retrieves diagnostic information for review purposes. Even in the context of a Meta Ads connector with other destructive tools (delete_ad, delete_ad_creative, delete_adset), this specific tool only performs retrieval operations.
From the tool's definition Tool name contains 'get' and description states 'Fetch aggregated catalog issues' - retrieves and queries data about catalog diagnostics without modifying or deleting anything.
Attacks that exploit this kind of access
Fetch aggregated catalog issues (rejected items, missing fields, image problems) from Meta. It is categorised as a Read tool in the Claude Meta MCP Server, which means it retrieves data without modifying state.
Register the Claude Meta MCP server in PolicyLayer and add a rule for get_catalog_diagnostics: 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 Claude Meta. Nothing to install.
get_catalog_diagnostics 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_catalog_diagnostics 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_catalog_diagnostics. 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_catalog_diagnostics is provided by the Claude Meta MCP server (maxx3250/claude-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 →