Replace a Frida script under /data/system/junge/<pkg>/frida and verify the write.
AI agents use replace_frida_script 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.
This tool writes/overwrites a Frida script file on the device filesystem. While 'replace' is a write operation (creating or modifying content), the prior script content is overwritten which could be considered destructive. However, it's a file write to a known path that could potentially be restored, placing it in Write.
From the tool's definition Replace a Frida script under /data/system/junge/<pkg>/frida and verify the write
Documented attack patterns abuse exactly the kind of access replace_frida_script 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 replace_frida_script:
{
"version": "1",
"default": "deny",
"tools": {
"replace_frida_script": {
"limits": [
{
"counter": "replace_frida_script_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}replace_frida_script 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.
Replace a Frida script under /data/system/junge/<pkg>/frida and verify the write. 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 replace_frida_script: 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.
replace_frida_script 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 replace_frida_script 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 replace_frida_script. 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.
replace_frida_script 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.