omarchy_tailscale_receive
Save incoming Taildrop files and announce them [group:tailscale] Args: [--once] [directory]
This record as markdown: /tools/omarchy-mcp/omarchy-tailscale-receive.md
What omarchy_tailscale_receive does on Omarchy-MCP
AI agents use omarchy_tailscale_receive to create or update resources in Omarchy-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Omarchy-MCP environment.
Why omarchy_tailscale_receive is rated Medium
Tool writes received files to disk; potential for overwriting or filling storage with untrusted content.
From the tool's definition Save incoming Taildrop files and announce them
Attacks that exploit this kind of access
The rule that runs omarchy_tailscale_receive safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For omarchy_tailscale_receive, this is the rule to start with:
omarchy_tailscale_receive 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 Omarchy-MCP, apply this rule, and every omarchy_tailscale_receive call is checked against it from then on.
Questions about omarchy_tailscale_receive
Save incoming Taildrop files and announce them [group:tailscale] Args: [--once] [directory]. It is categorised as a Write tool in the Omarchy-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Omarchy MCP server in PolicyLayer and add a rule for omarchy_tailscale_receive: 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 Omarchy-MCP. Nothing to install.
omarchy_tailscale_receive 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 omarchy_tailscale_receive 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 omarchy_tailscale_receive. 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.
omarchy_tailscale_receive is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Omarchy, and thousands of servers like it.
This server
Across the catalogue