AI agents use add_movie_by_id to create or update resources in Arr Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Arr Assistant environment.
This tool creates new entries in a media management system (Radarr) by adding movies. While it modifies state reversibly (movies can be removed from the library), it does not delete, execute arbitrary code, or move money. The medium severity reflects that misuse could bulk-add unwanted content to a user's media library, but the effects are reversible and limited to media metadata rather than system-level damage.
From the tool's definition Tool description states 'Add a specific movie to Radarr', which creates/modifies data in an external service (Radarr media library) through the MCP server.
Documented attack patterns abuse exactly the kind of access add_movie_by_id 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 add_movie_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"add_movie_by_id": {
"limits": [
{
"counter": "add_movie_by_id_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_movie_by_id stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a specific movie to Radarr using its TMDb ID. It is categorised as a Write tool in the Arr Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Arr Assistant MCP server in PolicyLayer and add a rule for add_movie_by_id: 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.
add_movie_by_id is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_movie_by_id 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 add_movie_by_id. 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.
add_movie_by_id 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.