getUserPreferences
Read the calling user's preferences. Self-only — no params required. Returns { notifications, grids } where notifications is the single notification-preferences row and grids is an array of per-grid view rows. Read-only.
This record as markdown: /tools/io-stablebaseline-sb/getuserpreferences.md
What getUserPreferences does on Stable Baseline
AI agents call getUserPreferences to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getUserPreferences is rated Low
This tool retrieves user-scoped preference data with no side effects or modifications. It operates in a self-only context (the calling user's own data), making it a straightforward read operation with minimal security impact. Low severity because the blast radius is confined to the user's own preferences, which contain no sensitive financial, operational, or destructive capabilities.
From the tool's definition Tool description explicitly states 'Read-only' and 'Read the calling user's preferences'. It takes no parameters and returns only the user's own notification and grid view preferences.
Attacks that exploit this kind of access
The rule that runs getUserPreferences safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getUserPreferences, this is the rule to start with:
getUserPreferences is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every getUserPreferences call is checked against it from then on.
Questions about getUserPreferences
Read the calling user's preferences. Self-only — no params required. Returns { notifications, grids } where notifications is the single notification-preferences row and grids is an array of per-grid view rows. Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for getUserPreferences: 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 Stable Baseline. Nothing to install.
getUserPreferences 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 getUserPreferences 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 getUserPreferences. 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.
getUserPreferences is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue