bluesky_action
Perform a Bluesky action: bluesky_post, bluesky_read_feed, bluesky_reply, bluesky_like, bluesky_repost, bluesky_search, bluesky_profile, bluesky_follow.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bluesky-action.md
What bluesky_action does on UnClick
AI agents invoke bluesky_action to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
cid | string | — | |
uri | string | — | |
text | string | — | |
actor | string | — | |
limit | number | — | |
query | string | — | |
action | string | Yes | |
password | string | — | App password |
identifier | string | — | Bluesky handle or DID |
Parameters from the server's own tool schema.
Why bluesky_action is rated High
This tool spans multiple categories depending on the action argument. It includes Read operations (bluesky_read_feed, bluesky_search, bluesky_profile) but also Write/Execute operations (bluesky_post, bluesky_reply, bluesky_like, bluesky_repost, bluesky_follow) that trigger external social media actions. Per rules, the most severe applicable category is chosen.
From the tool's definition Perform a Bluesky action: bluesky_post, bluesky_reply, bluesky_like, bluesky_repost, bluesky_search, bluesky_profile, bluesky_follow
Risk signalsAccepts URL/endpoint input (uri) · Handles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs bluesky_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bluesky_action, this is the rule to start with:
bluesky_action 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 UnClick, apply this rule, and every bluesky_action call is checked against it from then on.
Questions about bluesky_action
Perform a Bluesky action: bluesky_post, bluesky_read_feed, bluesky_reply, bluesky_like, bluesky_repost, bluesky_search, bluesky_profile, bluesky_follow. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
bluesky_action accepts 9 parameters: cid, uri, text, actor, limit, query, action, password, identifier. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for bluesky_action: 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 UnClick. Nothing to install.
bluesky_action 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 bluesky_action 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 bluesky_action. 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.
bluesky_action is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue