List paired Meta Ray-Ban Meta (Gen 2) glasses devices and their connection state.
AI agents call crow_glasses_status to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and lists the status of paired glasses devices and their connection states. It retrieves data without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is minimal—an agent could at worst learn what glasses are paired, which is low-risk information disclosure.
From the tool's definition Tool description states 'List paired Meta Ray-Ban Meta (Gen 2) glasses devices and their connection state' — a query operation that retrieves device information without modification or side effects.
Documented attack patterns abuse exactly the kind of access crow_glasses_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_glasses_status:
{
"version": "1",
"default": "deny",
"tools": {
"crow_glasses_status": {}
}
} crow_glasses_status 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.
List paired Meta Ray-Ban Meta (Gen 2) glasses devices and their connection state. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_glasses_status: 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 Crow. Nothing to install.
crow_glasses_status 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 crow_glasses_status 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 crow_glasses_status. 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.
crow_glasses_status is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.