status_reblog · Mastodon MCP: Risk & Policy

WHAT IT DOES

What status_reblog does on Mastodon

AI agents use status_reblog 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.

WHY IT NEEDS A POLICY

Why status_reblog needs a policy

Reblogging/boosting a status creates a new entry on the user's timeline that shares the original content. This is a reversible write action (boosts can be undone), not destructive or financial. Misuse could spread misinformation or spam, giving it medium severity.

From the tool's definition Reblog (boost) a status

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

status_reblog Rate-limited

status_reblog 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "status_reblog": {
      "limits": [
        {
          "counter": "status_reblog_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mastodon, so you can run agents against it safely.

FAQ

Questions about status_reblog

What does the status_reblog tool do? +

Reblog (boost) a status. 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.

How do I enforce a policy on status_reblog? +

Register the Mastodon MCP server in PolicyLayer and add a rule for status_reblog: 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.

What risk level is status_reblog? +

status_reblog is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit status_reblog? +

Yes. Add a rate_limit block to the status_reblog 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.

How do I block status_reblog completely? +

Set action: deny in the PolicyLayer policy for status_reblog. 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.

What MCP server provides status_reblog? +

status_reblog 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.