AI agents call fetch_show_recommendations to retrieve information from Trakt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches entertainment recommendations from Trakt, which is a read-only operation that retrieves data without modifying state. No side effects, no data destruction, no financial transactions, and no code execution. Confidence is slightly reduced due to the empty description, but the naming convention and server context strongly suggest a safe read operation.
From the tool's definition Tool name 'fetch_show_recommendations' indicates retrieval of recommendation data. Description is empty, but the pattern of sibling tools (fetch_anticipated_movies, fetch_anticipated_shows, fetch_boxoffice_movies, fetch_comment) all perform read-only data…
Documented attack patterns abuse exactly the kind of access fetch_show_recommendations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trakt, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_show_recommendations:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_show_recommendations": {}
}
}fetch_show_recommendations 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.
fetch_show_recommendations. It is categorised as a Read tool in the Trakt MCP Server, which means it retrieves data without modifying state.
Register the Trakt MCP server in PolicyLayer and add a rule for fetch_show_recommendations: 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 Trakt. Nothing to install.
fetch_show_recommendations 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 fetch_show_recommendations 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 fetch_show_recommendations. 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.
fetch_show_recommendations is provided by the Trakt MCP server (wwiens/trakt_mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 77 Trakt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
77 Trakt tools catalogued and risk-classified — across an index of 42,500+ MCP servers.