AI agents call os_voiceover_status to retrieve information from OScribe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current state of the VoiceOver screen reader on macOS without modifying any system settings, application state, or data. It is purely informational. While it is part of a desktop automation server with Execute-category tools (os_click, os_hotkey, os_drag), this specific tool only reads status and poses minimal security risk if misused by an AI agent.
From the tool's definition Tool description states 'Check VoiceOver screen reader status' - a query operation with no side effects. Returns status information only.
Attacks that exploit this kind of access
Check VoiceOver screen reader status (macOS only). VoiceOver is needed for Electron app accessibility. It is categorised as a Read tool in the OScribe MCP Server, which means it retrieves data without modifying state.
Register the OScribe MCP server in PolicyLayer and add a rule for os_voiceover_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 OScribe. Nothing to install.
os_voiceover_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 os_voiceover_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 os_voiceover_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.
os_voiceover_status is provided by the OScribe MCP server (mikealkeal/oscribe). 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 →