Get current user preferences including default model and cost preference
AI agents call get-user-preferences to retrieve information from Cross-LLM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration or preference data about the current user without creating, modifying, deleting, executing code, or committing financial obligations. It has minimal blast radius — exposure of user preferences could leak minor configuration details but poses no operational risk. Classified as Read with low severity.
From the tool's definition Tool name is 'get-user-preferences' and description states 'Get current user preferences' — the verb 'Get' indicates data retrieval with no modification. The description lists only read operations: retrieving 'default model and cost preference' settings.
Documented attack patterns abuse exactly the kind of access get-user-preferences gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cross-LLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-user-preferences:
{
"version": "1",
"default": "deny",
"tools": {
"get-user-preferences": {}
}
}get-user-preferences 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.
Get current user preferences including default model and cost preference. It is categorised as a Read tool in the Cross-LLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cross-LLM MCP Server MCP server in PolicyLayer and add a rule for get-user-preferences: 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 Cross-LLM MCP Server. Nothing to install.
get-user-preferences 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 get-user-preferences 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 get-user-preferences. 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.
get-user-preferences is provided by the Cross-LLM MCP Server MCP server (jamesanz/cross-llm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cross-LLM 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.
23 Cross-LLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.