Low Risk

camofox_query_selector

Query a CSS selector in the live DOM and return its element details or a specific attribute. Use this for targeted inspection without writing raw evaluate_js. Requires CAMOFOX_API_KEY.

How to control camofox_query_selector ↓

AI agents call camofox_query_selector to retrieve information from Camofox without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

camofox_query_selector performs DOM querying and attribute inspection only. It retrieves element details from the page without modifying state, executing code, deleting data, or triggering external operations. The tool is read-only and returns information about the page structure.

From the tool's definition Tool description states 'Query a CSS selector in the live DOM and return its element details or a specific attribute' and 'inspection without writing raw evaluate_js' — pure retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access camofox_query_selector gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Camofox, and nothing reaches the server without passing your rules. This is the rule we recommend for camofox_query_selector:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "camofox_query_selector": {}
  }
}

camofox_query_selector is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Camofox — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the camofox_query_selector tool do? +

Query a CSS selector in the live DOM and return its element details or a specific attribute. Use this for targeted inspection without writing raw evaluate_js. Requires CAMOFOX_API_KEY. It is categorised as a Read tool in the Camofox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on camofox_query_selector? +

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

What risk level is camofox_query_selector? +

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

Can I rate-limit camofox_query_selector? +

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

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

camofox_query_selector is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Camofox tool call.

Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.