Fetch full details for a single product catalog including name, vertical, product/feed counts and configuration.
AI agents call get_product_catalog 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 tool queries and retrieves existing product catalog information without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation that poses minimal security risk even if invoked by an AI agent, as it only exposes catalog metadata.
From the tool's definition Tool name is 'get_product_catalog' and description states 'Fetch full details for a single product catalog' — the verb 'Fetch' and the retrieval of product catalog metadata (name, vertical, counts, configuration) indicates a read-only operation with no data…
Attacks that exploit this kind of access
Fetch full details for a single product catalog including name, vertical, product/feed counts and configuration. 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_product_catalog: 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_product_catalog 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_product_catalog 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_product_catalog. 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_product_catalog 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 →