get-profile-ua
A read tool on the AdsPower LocalAPI MCP server.
This record as markdown: /tools/adspower-adspower-browser/get-profile-ua.md
What get-profile-ua does on AdsPower LocalAPI MCP Server
AI agents call get-profile-ua to retrieve information from AdsPower LocalAPI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-profile-ua is rated Low
This tool retrieves profile user-agent information, which is a read operation with no side effects. It queries existing data from an AdsPower browser profile without modifying or executing anything. The blast radius if misused is minimal—an agent could only gather UA metadata, not alter profiles or execute code.
From the tool's definition Tool name 'get-profile-ua' suggests retrieving a user-agent string from a browser profile. The naming convention ('get-*') indicates a read/query operation. No destructive, write, or execute keywords present. The empty description limits evidence specificity.
Attacks that exploit this kind of access
The rule that runs get-profile-ua 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 get-profile-ua, this is the rule to start with:
get-profile-ua 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 AdsPower LocalAPI MCP Server, apply this rule, and every get-profile-ua call is checked against it from then on.
Questions about get-profile-ua
get-profile-ua is a read tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Read tool in the AdsPower LocalAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for get-profile-ua: 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.
get-profile-ua 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-profile-ua 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-profile-ua. 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-profile-ua 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