mastodon_action
Perform a Mastodon action: mastodon_post, mastodon_read_timeline, mastodon_reply, mastodon_boost, mastodon_favorite, mastodon_search, mastodon_profile, mastodon_follow, mastodon_notifications.
This record as markdown: /tools/creativelead-unclick/mastodon-action.md
What mastodon_action does on UnClick
AI agents invoke mastodon_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 |
|---|---|---|---|
q | string | — | |
id | string | — | |
acct | string | — | |
action | string | — | |
status | string | — | |
access_token | string | — | |
instance_url | string | — | |
in_reply_to_id | string | — |
Parameters from the server's own tool schema.
Why mastodon_action is rated High
This tool bundles multiple distinct operations — some are Read (search, profile, notifications, read_timeline) and some are Write/Execute (post, reply, boost, favorite, follow). Since it can post content, reply, follow users, and boost/favorite posts on behalf of the user, the most severe applicable category is Execute (triggering external social operations).
From the tool's definition Perform a Mastodon action: mastodon_post, mastodon_reply, mastodon_boost, mastodon_favorite, mastodon_search, mastodon_profile, mastodon_follow, mastodon_notifications
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs mastodon_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 mastodon_action, this is the rule to start with:
mastodon_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 mastodon_action call is checked against it from then on.
Questions about mastodon_action
Perform a Mastodon action: mastodon_post, mastodon_read_timeline, mastodon_reply, mastodon_boost, mastodon_favorite, mastodon_search, mastodon_profile, mastodon_follow, mastodon_notifications. 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.
mastodon_action accepts 8 parameters: q, id, acct, action, status, access_token, instance_url, in_reply_to_id. 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 mastodon_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.
mastodon_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 mastodon_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 mastodon_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.
mastodon_action is provided by the UnClick MCP server (creativelead/unclick). 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