gts_status
Report GoToSocial instance health: reachability, admin account status, federation peer count, pending notifications, disk usage of the local media cache.
This record as markdown: /tools/kh0pper-crow/gts-status.md
What gts_status does on Crow
AI agents call gts_status to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gts_status is rated Low
gts_status is a read-only health check utility that queries and reports on system state metrics. It retrieves information about GoToSocial instance health but does not modify, execute operations, delete data, or commit financial actions. The blast radius of misuse is minimal—an AI agent calling this tool can only learn about system state, not affect it.
From the tool's definition Tool reports status information: 'reachability, admin account status, federation peer count, pending notifications, disk usage' — all queries that retrieve and display data without modification.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs gts_status 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_status, this is the rule to start with:
gts_status is read-only, so it stays allowed. 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 gts_status call is checked against it from then on.
Questions about gts_status
Report GoToSocial instance health: reachability, admin account status, federation peer count, pending notifications, disk usage of the local media cache. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for gts_status: 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.
gts_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gts_status 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 gts_status. 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.
gts_status 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