This record as markdown: /tools/heznpc-airmcp/tag-content.md
What tag_content does on AirMCP
AI agents invoke tag_content to trigger actions in AirMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why tag_content is rated High
The tool invokes an AI-driven classification and tagging operation, which is an external action that modifies metadata or labels associated with content. It spans Write (tagging modifies content metadata) and Execute (triggers an Apple Intelligence operation). Since it runs an external AI operation that modifies content attributes, Execute is the most accurate category.
From the tool's definition 'Classify and tag content using Apple' — triggers an Apple Intelligence classification/tagging operation on content
Attacks that exploit this kind of access
The rule that runs tag_content 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 tag_content, this is the rule to start with:
tag_content stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 tag_content call is checked against it from then on.
Questions about tag_content
Classify and tag content using Apple. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for tag_content: 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.
tag_content is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tag_content 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 tag_content. 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.
tag_content 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