Check the status and connectivity of Radarr and Sonarr servers.
AI agents call get_server_status to retrieve information from Arr Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic check of server status and connectivity. It retrieves information about the operational state of Radarr and Sonarr services but does not create, modify, delete, execute commands, or commit financial transactions. It is a safe read operation with minimal blast radius if misused—at worst, an AI agent would repeatedly poll status information without causing harm.
From the tool's definition Tool name 'get_server_status' and description 'Check the status and connectivity' indicate a read-only query operation that retrieves status information without modifying any data or triggering actions.
Documented attack patterns abuse exactly the kind of access get_server_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Arr Assistant, and nothing reaches the server without passing your rules. This is the rule we recommend for get_server_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_server_status": {}
}
}get_server_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.
Check the status and connectivity of Radarr and Sonarr servers. It is categorised as a Read tool in the Arr Assistant MCP Server, which means it retrieves data without modifying state.
Register the Arr Assistant MCP server in PolicyLayer and add a rule for get_server_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 Arr Assistant. Nothing to install.
get_server_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 get_server_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 get_server_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.
get_server_status is provided by the Arr Assistant MCP server (omniwaifu/arr-assistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Arr Assistant, 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.
6 Arr Assistant tools catalogued and risk-classified — across an index of 43,000+ MCP servers.