Report GoToSocial instance health: reachability, admin account status, federation peer count, pending notifications, disk usage of the local media cache.
AI agents call gts_status to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and reports status information about a GoToSocial instance. It performs read-only queries of system metrics and state without creating, modifying, or deleting any data. The blast radius of misuse is minimal—an attacker gains visibility into instance health but cannot alter configurations, delete data, or trigger actions. This is a classic Read operation.
From the tool's definition The tool 'gts_status' reports instance health metrics including reachability, admin account status, federation peer count, pending notifications, and disk usage. Action verbs are 'Report' and implicit 'query/retrieve'.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access gts_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for gts_status:
{
"version": "1",
"default": "deny",
"tools": {
"gts_status": {}
}
} gts_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.