unfollow_selected
Unfollow exactly the handles you name: searches the following list, presses the row button, confirms. Dry run unless confirm:true
This record as markdown: /tools/0click-insta/unfollow-selected.md
What unfollow_selected does on 0click Insta
AI agents invoke unfollow_selected to trigger actions in 0click Insta. 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 unfollow_selected is rated High
unfollow_selected triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs unfollow_selected safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0click Insta, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unfollow_selected, this is the rule to start with:
unfollow_selected 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 0click Insta, apply this rule, and every unfollow_selected call is checked against it from then on.
Questions about unfollow_selected
Unfollow exactly the handles you name: searches the following list, presses the row button, confirms. Dry run unless confirm:true. It is categorised as a Execute tool in the 0click Insta MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 0click Insta MCP server in PolicyLayer and add a rule for unfollow_selected: 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 0click Insta. Nothing to install.
unfollow_selected 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 unfollow_selected 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 unfollow_selected. 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.
unfollow_selected is provided by the 0click Insta MCP server (akufikri/0click-insta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0click Insta, and thousands of servers like it.
Across the catalogue