gts_post

Publish a status (toot) to the fediverse. Content is public by default unless visibility is narrowed. Rate-limited: 10/hour per conversation.

SERVERCrow SOURCEkh0pper/crow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/gts-post.md

WHAT IT DOES

What gts_post does on Crow

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

RISK

Why gts_post is rated Medium

This tool creates and publishes new content (a fediverse status/toot) to a public or semi-public audience. It is reversible (posts can typically be deleted), so it does not rise to Destructive. The action is Write rather than Execute because it creates content via a specific API rather than executing arbitrary code.

From the tool's definition Tool description explicitly states 'Publish a status (toot) to the fediverse' and 'Content is public by default unless visibility is narrowed.' The verb 'publish' and action of creating a status demonstrates write capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gts_post 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 gts_post, this is the rule to start with:

gts_post Rate-limited

gts_post 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": {
    "gts_post": {
      "limits": [
        {
          "counter": "gts_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every gts_post call is checked against it from then on.

FAQ

Questions about gts_post

What does the gts_post tool do? +

Publish a status (toot) to the fediverse. Content is public by default unless visibility is narrowed. Rate-limited: 10/hour per conversation. 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.

How do I enforce a policy on gts_post? +

Register the Crow MCP server in PolicyLayer and add a rule for gts_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 Crow. Nothing to install.

What risk level is gts_post? +

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

Can I rate-limit gts_post? +

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

How do I block gts_post completely? +

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

What MCP server provides gts_post? +

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

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →