move-browser
A write tool on the AdsPower LocalAPI MCP server.
This record as markdown: /tools/adspower-adspower-browser/move-browser.md
What move-browser does on AdsPower LocalAPI MCP Server
AI agents use move-browser to create or update resources in AdsPower LocalAPI MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdsPower LocalAPI MCP Server environment.
Why move-browser is rated Medium
The name 'move-browser' suggests relocating or reassigning a browser profile (e.g., to a different group), which is a reversible write/update operation. Confidence is reduced due to the empty description. Given sibling tools like 'create-browser', 'delete-browser', and 'create-group', moving a browser likely means reassigning it to a group, which is a Write operation.
From the tool's definition Tool name 'move-browser' on a server managing browser profiles; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs move-browser safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdsPower LocalAPI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move-browser, this is the rule to start with:
move-browser 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 AdsPower LocalAPI MCP Server, apply this rule, and every move-browser call is checked against it from then on.
Questions about move-browser
move-browser is a write tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Write tool in the AdsPower LocalAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for move-browser: 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 AdsPower LocalAPI MCP Server. Nothing to install.
move-browser 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 move-browser 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 move-browser. 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.
move-browser is provided by the AdsPower LocalAPI MCP Server MCP server (adspower/adspower-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdsPower LocalAPI MCP Server, and thousands of servers like it.
This server
Across the catalogue