AI agents use media_post to create or update resources in Mastodon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mastodon environment.
The tool creates or uploads media content to Mastodon, which is a reversible write operation. While the description is empty, the name and server context clearly indicate content creation. Severity is medium because posting content can amplify misinformation or unwanted material, but the action is reversible (media can be deleted).
From the tool's definition Tool name 'media_post' in Mastodon MCP server context suggests creating/uploading media content. Server description states the tool enables 'post statuses' and 'manage accounts' on Mastodon instances.
Attacks that exploit this kind of access
media_post. It is categorised as a Write tool in the Mastodon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mastodon MCP server in PolicyLayer and add a rule for media_post: 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 Mastodon. Nothing to install.
media_post 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 media_post 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 media_post. 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.
media_post is provided by the Mastodon MCP server (vitexsoftware/mastodon-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
media_post is one line of Mastodon's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →