Medium Risk

hide_show_recommendation

MCP tool: hide a show from future recommendations.

How to control hide_show_recommendation ↓

AI agents use hide_show_recommendation to create or update resources in Trakt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trakt environment.

Medium Risk

This tool modifies the user's recommendation preferences by hiding a show, which is a reversible write operation (the show could presumably be unhidden). It has minimal blast radius as it only affects future recommendation results for the user.

From the tool's definition hide a show from future recommendations

Documented attack patterns abuse exactly the kind of access hide_show_recommendation 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 hide_show_recommendation:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hide_show_recommendation": {
      "limits": [
        {
          "counter": "hide_show_recommendation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

hide_show_recommendation 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.

  1. Create a free account and register Trakt — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the hide_show_recommendation tool do? +

MCP tool: hide a show from future recommendations. It is categorised as a Write tool in the Trakt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on hide_show_recommendation? +

Register the Trakt MCP server in PolicyLayer and add a rule for hide_show_recommendation: 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.

What risk level is hide_show_recommendation? +

hide_show_recommendation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hide_show_recommendation? +

Yes. Add a rate_limit block to the hide_show_recommendation 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.

How do I block hide_show_recommendation completely? +

Set action: deny in the PolicyLayer policy for hide_show_recommendation. 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.

What MCP server provides hide_show_recommendation? +

hide_show_recommendation 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.

Enforce policy on every Trakt tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.