wavexis_get_pref
Get a browser preference value by key.
This record as markdown: /tools/wavexis-mcp/wavexis-get-pref.md
What wavexis_get_pref does on Wavexis
AI agents call wavexis_get_pref to retrieve information from Wavexis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wavexis_get_pref is rated Low
This tool retrieves configuration/preference data from the browser without any side effects. It matches the 'Read' category definition: queries data with no side effects. The severity is low because accessing browser preferences poses minimal risk; an agent could learn about browser settings but cannot modify state or trigger external operations.
From the tool's definition Tool name is 'wavexis_get_pref' and description states 'Get a browser preference value by key' — explicitly a retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs wavexis_get_pref safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_get_pref, this is the rule to start with:
wavexis_get_pref 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 Wavexis, apply this rule, and every wavexis_get_pref call is checked against it from then on.
Questions about wavexis_get_pref
Get a browser preference value by key. It is categorised as a Read tool in the Wavexis MCP Server, which means it retrieves data without modifying state.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_get_pref: 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 Wavexis. Nothing to install.
wavexis_get_pref 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 wavexis_get_pref 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 wavexis_get_pref. 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.
wavexis_get_pref is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
This server
Across the catalogue