mastodon_post_with_media
Upload an image/video and publish it as a status. Uploads via POST /api/v2/media (async processing) then POST /api/v1/statuses. Pass file_path OR file_base64+filename. Rate-limited: 10/hour.
This record as markdown: /tools/kh0pper-crow/mastodon-post-with-media.md
What mastodon_post_with_media does on Crow
AI agents use mastodon_post_with_media to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why mastodon_post_with_media is rated Medium
The tool creates and publishes new content (a status with media) to a social media platform, which is reversible (statuses can be deleted). This is a Write operation rather than Execute because it performs a specific, bounded action (publish a status) rather than arbitrary code execution.
From the tool's definition Tool description states 'Upload an image/video and publish it as a status' with POST requests to media and statuses endpoints. This creates new content on the Mastodon platform.
Attacks that exploit this kind of access
The rule that runs mastodon_post_with_media safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mastodon_post_with_media, this is the rule to start with:
mastodon_post_with_media 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 Crow, apply this rule, and every mastodon_post_with_media call is checked against it from then on.
Questions about mastodon_post_with_media
Upload an image/video and publish it as a status. Uploads via POST /api/v2/media (async processing) then POST /api/v1/statuses. Pass file_path OR file_base64+filename. Rate-limited: 10/hour. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for mastodon_post_with_media: 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 Crow. Nothing to install.
mastodon_post_with_media 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 mastodon_post_with_media 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_post_with_media. 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_post_with_media is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue