Low Risk

get_preference_list

Retrieves the user's preference list.

How to control get_preference_list ↓

What get_preference_list does on RSS MCP Server

AI agents call get_preference_list to retrieve information from RSS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_preference_list needs a policy

The tool retrieves preference data (a read-only operation) with no capacity to modify, delete, execute code, or affect finances. The blast radius of misuse is minimal—an agent could only access the user's stored preferences, not alter system state or expose sensitive operations. This falls squarely under the 'Read' category with low severity.

From the tool's definition Tool name 'get_preference_list' and description 'Retrieves the user's preference list' indicate a query operation that fetches configuration data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_preference_list gives an agent:

How to control get_preference_list

PolicyLayer is an MCP gateway — it sits between your AI agents and RSS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_preference_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_preference_list": {}
  }
}

get_preference_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register RSS MCP Server — 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_preference_list

What does the get_preference_list tool do? +

Retrieves the user's preference list. It is categorised as a Read tool in the RSS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_preference_list? +

Register the RSS MCP Server MCP server in PolicyLayer and add a rule for get_preference_list: 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 RSS MCP Server. Nothing to install.

What risk level is get_preference_list? +

get_preference_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_preference_list? +

Yes. Add a rate_limit block to the get_preference_list 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 get_preference_list completely? +

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

get_preference_list is provided by the RSS MCP Server MCP server (xueli-sherryli/rss-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RSS MCP Server tool call.

Start from RSS MCP Server, 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.

34 RSS MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.