This record as markdown: /tools/heznpc-airmcp/ai-status.md
What ai_status does on AirMCP
AI agents call ai_status to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ai_status is rated Low
This tool checks the availability and status of Apple Intelligence services—a passive information retrieval operation. It does not create, modify, delete, execute code, or involve financial transactions. The verb 'check' combined with 'status' and 'availability' confirms read-only semantics.
From the tool's definition Tool name 'ai_status' and description 'Check availability and status of Apple' indicate a read-only query operation that retrieves status information without modifying or executing any side effects.
Attacks that exploit this kind of access
The rule that runs ai_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ai_status, this is the rule to start with:
ai_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every ai_status call is checked against it from then on.
Questions about ai_status
Check availability and status of Apple. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for ai_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 AirMCP. Nothing to install.
ai_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 ai_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 ai_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.
ai_status is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue