Add or replace custom hook entries, then sync config, AppSwitch, LSPosed, and optionally relaunch the target.
AI agents invoke add_custom_hooks to trigger actions in Algorithmaide. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool does more than just write data — it triggers a chain of external operations: syncing configuration across multiple subsystems (AppSwitch, LSPosed), and optionally relaunching the target application. The 'relaunch the target' and multi-system sync make this Execute-level. Misuse could inject malicious hooks into a running Android process or alter LSPosed module scope, making the blast radius high.
From the tool's definition Add or replace custom hook entries, then sync config, AppSwitch, LSPosed, and optionally relaunch the target
Documented attack patterns abuse exactly the kind of access add_custom_hooks 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 add_custom_hooks:
{
"version": "1",
"default": "deny",
"tools": {
"add_custom_hooks": {
"limits": [
{
"counter": "add_custom_hooks_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}add_custom_hooks stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add or replace custom hook entries, then sync config, AppSwitch, LSPosed, and optionally relaunch the target. It is categorised as a Execute tool in the Algorithmaide MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Algorithmaide MCP server in PolicyLayer and add a rule for add_custom_hooks: 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.
add_custom_hooks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the add_custom_hooks 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 add_custom_hooks. 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.
add_custom_hooks 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.