AI agents use account_mute 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.
Muting an account is a reversible social action that modifies the user's content filtering settings. It does not delete data or execute code, and it can be undone with an unmute operation, placing it in the Write category.
From the tool's definition 'Mute an account' — muting suppresses content from a user but is reversible (can be unmuted)
Attacks that exploit this kind of access
Mute an account. 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 account_mute: 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.
account_mute 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 account_mute 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 account_mute. 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.
account_mute 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →