This record as markdown: /tools/heznpc-airmcp/set-file-tags.md
What set_file_tags does on AirMCP
AI agents use set_file_tags to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why set_file_tags is rated Medium
This tool modifies file attributes (Finder tags) reversibly. While it does overwrite existing tags, the operation is non-destructive (tags can be re-set), affects only metadata not file content, has minimal blast radius if misused by an agent, and falls squarely into Write operations that create or modify data reversibly. It does not delete files, execute commands, or cause irreversible harm.
From the tool's definition The tool description states it 'Set Finder tags on a file' and 'Replaces all existing tags.' This is a direct modification of file metadata.
Attacks that exploit this kind of access
The rule that runs set_file_tags 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 set_file_tags, this is the rule to start with:
set_file_tags stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 set_file_tags call is checked against it from then on.
Questions about set_file_tags
Set Finder tags on a file. Replaces all existing tags. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for set_file_tags: 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.
set_file_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_file_tags 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 set_file_tags. 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.
set_file_tags 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