Resolve a semantic element query into stable refs for interaction workflows.
AI agents call oc_query to retrieve information from OpenChrome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
oc_query performs a read-only semantic resolution of page elements, returning references for later use in interaction workflows. It does not execute actions, modify data, delete anything, or commit financial transactions. While it operates within a browser automation context, the tool itself only queries and returns metadata (stable refs), making it a Read category tool with low severity.
From the tool's definition Tool description states it 'Resolve[s] a semantic element query into stable refs' — this is a query operation that retrieves element references without modifying state. The verb 'resolve' indicates lookup/retrieval, not modification or execution of actions.
Documented attack patterns abuse exactly the kind of access oc_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for oc_query:
{
"version": "1",
"default": "deny",
"tools": {
"oc_query": {}
}
}oc_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Resolve a semantic element query into stable refs for interaction workflows. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.
Register the OpenChrome MCP server in PolicyLayer and add a rule for oc_query: 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 OpenChrome. Nothing to install.
oc_query 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 oc_query 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 oc_query. 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.
oc_query is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.