Validate Prowlarr connection and configuration
AI agents call check-configuration to retrieve information from Yarr Media Stack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and validates configuration state (connection status, settings) without creating, modifying, deleting, or executing operations. It is a diagnostic read-only operation with minimal blast radius if misused—an AI agent calling this repeatedly would only waste resources or trigger rate limits, not cause data loss, unauthorized changes, or financial impact.
From the tool's definition Tool name 'check-configuration' and description 'Validate Prowlarr connection and configuration' indicate this performs validation/verification of existing configuration without modifying it.
Attacks that exploit this kind of access
Validate Prowlarr connection and configuration. It is categorised as a Read tool in the Yarr Media Stack MCP Server, which means it retrieves data without modifying state.
Register the Yarr Media Stack MCP server in PolicyLayer and add a rule for check-configuration: 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 Yarr Media Stack. Nothing to install.
check-configuration 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 check-configuration 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 check-configuration. 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.
check-configuration is provided by the Yarr Media Stack MCP server (mcpnexus-registry/yarr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →