Sync the LSPosed scope for AlgorithmAide and return the readback.
AI agents use sync_lsposed_scope to create or update resources in Algorithmaide — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Algorithmaide environment.
Syncing the LSPosed scope modifies the module's target application list on the device — a write/configuration operation that can alter which apps are hooked by LSPosed. It returns a readback (read component), but the primary effect is updating scope configuration. This is reversible (scope can be re-synced), so Write is appropriate rather than Destructive.
From the tool's definition Sync the LSPosed scope for AlgorithmAide and return the readback
Documented attack patterns abuse exactly the kind of access sync_lsposed_scope gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Algorithmaide, and nothing reaches the server without passing your rules. This is the rule we recommend for sync_lsposed_scope:
{
"version": "1",
"default": "deny",
"tools": {
"sync_lsposed_scope": {
"limits": [
{
"counter": "sync_lsposed_scope_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sync_lsposed_scope 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.
Free to start. No card required.
Sync the LSPosed scope for AlgorithmAide and return the readback. It is categorised as a Write tool in the Algorithmaide MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Algorithmaide MCP server in PolicyLayer and add a rule for sync_lsposed_scope: 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 Algorithmaide. Nothing to install.
sync_lsposed_scope 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 sync_lsposed_scope 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 sync_lsposed_scope. 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.
sync_lsposed_scope is provided by the Algorithmaide MCP server (vwww-droid/algorithmaide-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Algorithmaide, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Algorithmaide tools catalogued and risk-classified — across an index of 43,000+ MCP servers.