wavexis_set_user_agent
Set a custom User-Agent string for all subsequent requests.
This record as markdown: /tools/wavexis-mcp/wavexis-set-user-agent.md
What wavexis_set_user_agent does on Wavexis
AI agents use wavexis_set_user_agent to create or update resources in Wavexis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wavexis environment.
Why wavexis_set_user_agent is rated Medium
This tool modifies browser configuration (the User-Agent header) that affects all future network requests. It's a reversible configuration change (Write), not destructive, but it could be misused to impersonate other browsers/clients or bypass bot detection. Medium severity because it affects the behavior of subsequent browser actions but doesn't directly cause harm on its own.
From the tool's definition Set a custom User-Agent string for all subsequent requests
Attacks that exploit this kind of access
The rule that runs wavexis_set_user_agent 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_set_user_agent, this is the rule to start with:
wavexis_set_user_agent 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Wavexis, apply this rule, and every wavexis_set_user_agent call is checked against it from then on.
Questions about wavexis_set_user_agent
Set a custom User-Agent string for all subsequent requests. It is categorised as a Write tool in the Wavexis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_set_user_agent: 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_set_user_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wavexis_set_user_agent 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_set_user_agent. 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_set_user_agent 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