Get compact Arc inventory, counts, source health, and live context when available.
AI agents call arc_get_overview to retrieve information from Arc Browser MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves summary information about Arc Browser state (inventory counts, health status, context) without performing any actions that create, modify, delete, or execute operations. It is a straightforward read operation with minimal risk if misused by an AI agent—worst case being information disclosure about the user's browser state, which poses no direct harm.
From the tool's definition Tool name 'arc_get_overview' and description 'Get compact Arc inventory, counts, source health, and live context' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
Get compact Arc inventory, counts, source health, and live context when available. It is categorised as a Read tool in the Arc Browser MCP MCP Server, which means it retrieves data without modifying state.
Register the Arc Browser MCP server in PolicyLayer and add a rule for arc_get_overview: 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 Arc Browser MCP. Nothing to install.
arc_get_overview 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 arc_get_overview 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 arc_get_overview. 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.
arc_get_overview is provided by the Arc Browser MCP server (jasoncronje/arc-browser-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 →