AI agents call test_config 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 read-only diagnostic check of configuration and connectivity. It retrieves or queries the state of the system without side effects—no data is created, modified, deleted, or executed. Similar to the sibling 'get_server_status' tool, it belongs in the Read category. The severity is low because misuse would at worst cause unnecessary diagnostic calls with no impact on the system or data.
From the tool's definition Tool name 'test_config' and description 'Test the current configuration and API connectivity' indicate a diagnostic/query operation that checks status without modifying, creating, or deleting data.
Documented attack patterns abuse exactly the kind of access test_config 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 test_config:
{
"version": "1",
"default": "deny",
"tools": {
"test_config": {}
}
}test_config 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.
Test the current configuration and API connectivity. 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 test_config: 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.
test_config 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 test_config 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 test_config. 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.
test_config 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.