diagnose_pixel_on_site
AI agents call diagnose_pixel_on_site to retrieve information from KonQuest Meta Ads MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to diagnose (inspect/analyze) Meta ad tracking pixels on a website, which is a diagnostic read operation that queries or validates pixel configuration without altering it. Confidence is moderate (0.7) due to empty description—if it actually modifies pixel settings, it would be Write; if it executes code, it could be Execute. However, the name strongly suggests passive inspection.
From the tool's definition Tool name 'diagnose_pixel_on_site' suggests inspection/analysis of Meta tracking pixels without modification. No description provided.
Attacks that exploit this kind of access
diagnose_pixel_on_site. It is categorised as a Read tool in the KonQuest Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for diagnose_pixel_on_site: 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 KonQuest Meta Ads MCP. Nothing to install.
diagnose_pixel_on_site 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 diagnose_pixel_on_site 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 diagnose_pixel_on_site. 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.
diagnose_pixel_on_site is provided by the KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-ads-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 →