AI agents call sonarr.calendar to retrieve information from Arr Stack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'calendar' in Sonarr (a media server management tool) typically retrieves upcoming episode schedules or release calendars. This is a read-only query operation with no side effects. The absence of a description lowers confidence slightly, but the naming pattern and context of sibling read-only tools strongly indicates data retrieval rather than modification, execution, or deletion.
From the tool's definition Tool name 'sonarr.calendar' combined with the pattern of sibling tools (search, list, now_playing, recent_additions, system_info, users_list, artist_albums) suggests this retrieves calendar/schedule data. No description provided.
Attacks that exploit this kind of access
sonarr.calendar. It is categorised as a Read tool in the Arr Stack MCP Server, which means it retrieves data without modifying state.
Register the Arr Stack MCP server in PolicyLayer and add a rule for sonarr.calendar: 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 Stack. Nothing to install.
sonarr.calendar 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 sonarr.calendar 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 sonarr.calendar. 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.
sonarr.calendar is provided by the Arr Stack MCP server (new-usemame/arr-stack-mcp). 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 →