semantic_clear
Delete all indexed data from the local vector store AND remove corresponding entries from macOS Spotlight.
This record as markdown: /tools/heznpc-airmcp/semantic-clear.md
What semantic_clear does on AirMCP
AI agents call semantic_clear to permanently remove resources in AirMCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why semantic_clear is rated Critical
This tool performs irreversible deletion of indexed data across two systems (local vector store and macOS Spotlight). The action cannot be undone and results in permanent loss of searchability and indexed content. While not affecting user-created files directly, it destroys the indexing layer that enables search functionality across the Apple ecosystem tools on this server, making it Destructive rather than Write.
From the tool's definition "Delete all indexed data from the local vector store AND remove corresponding entries from macOS Spotlight" — uses "Delete" and describes irreversible removal of indexed data and Spotlight entries without recovery mechanism.
Attacks that exploit this kind of access
The rule that runs semantic_clear 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 semantic_clear, this is the rule to start with:
semantic_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every semantic_clear call is checked against it from then on.
Questions about semantic_clear
Delete all indexed data from the local vector store AND remove corresponding entries from macOS Spotlight. It is categorised as a Destructive tool in the AirMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Air MCP server in PolicyLayer and add a rule for semantic_clear: 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.
semantic_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the semantic_clear 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 semantic_clear. 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.
semantic_clear 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.
Across the catalogue