share-profile
A write tool on the AdsPower LocalAPI MCP server.
This record as markdown: /tools/adspower-adspower-browser/share-profile.md
What share-profile does on AdsPower LocalAPI MCP Server
AI agents use share-profile 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 share-profile is rated Medium
This tool most likely creates, modifies, or changes permissions related to browser profile sharing. This is a Write operation as it reversibly modifies profile metadata or sharing configuration rather than reading data (Read), executing arbitrary commands (Execute), permanently deleting resources (Destructive), or handling financial transactions (Financial).
From the tool's definition Tool named 'share-profile' on AdsPower LocalAPI MCP Server that manages browser profiles with custom fingerprints. Sibling tools include create-browser, create-group, create-proxy, and delete-browser, indicating profile manipulation capabilities.
Attacks that exploit this kind of access
The rule that runs share-profile 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 share-profile, this is the rule to start with:
share-profile 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 share-profile call is checked against it from then on.
Questions about share-profile
share-profile 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 share-profile: 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.
share-profile 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 share-profile 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 share-profile. 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.
share-profile 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