get_product_context

SERVERAd Lab SOURCE@577-tools/ad-lab-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/577-tools-ad-lab-mcp/get-product-context.md

WHAT IT DOES

What get_product_context does on Ad Lab

AI agents call get_product_context to retrieve information from Ad Lab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_product_context is rated Low

Even though get_product_context only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_product_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ad Lab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_product_context, this is the rule to start with:

get_product_context Allowed

get_product_context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_product_context": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ad Lab, apply this rule, and every get_product_context call is checked against it from then on.

FAQ

Questions about get_product_context

What does the get_product_context tool do? +

Fetch the Ad Lab context bundle for a product: knowledge (product_md, carousel_profile, deep_profile), brand_voice, claim_safety, brand_docs (all brand markdown keyed by slug; READ adgenius-playbook, winning-copy-formulas, winning-ad-styles, ad-lab-agent-playbook before drafting), testimonials, testimonials_mapping, packshots (signed URLs), winners, losers, and rejected_lessons (reject reasons = what NOT to do). It is categorised as a Read tool in the Ad Lab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_product_context? +

Register the Ad Lab MCP server in PolicyLayer and add a rule for get_product_context: 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 Ad Lab. Nothing to install.

What risk level is get_product_context? +

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

Can I rate-limit get_product_context? +

Yes. Add a rate_limit block to the get_product_context 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 get_product_context completely? +

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

get_product_context is provided by the Ad Lab MCP server (@577-tools/ad-lab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ad Lab, and thousands of servers like it.

This server

All 13 Ad Lab tools →

Across the catalogue

get_product_data on 08-AI-Business-Agent →shopify_get_product on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →editor_context on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →