// MCP TOOL REFERENCE

ALGORITHMAIDE TOOLS

23 tools from the Algorithmaide MCP Server, categorised by risk level.

// ALL 23 ALGORITHMAIDE TOOLS

READ 11 tools

Read collect_exported_logs Compatibility tool for pulling legacy exported log files only. Read collect_runtime_logs Collect runtime logs, prioritizing the SQLite database and frida.log. Read get_hook_log_context Expand one structured hook log entry into a short surrounding time-window context. Read inspect_hook_candidate Summarize one dynamic candidate into short hits, short context, jadx-ai-mcp hints, and draft add_custom_hoo... Read list_hook_packs List built-in hook templates that can be applied to a target app. Read list_hook_profiles List locally saved hook configuration profiles. Read query_agent_logs Build a short unified log view from sqlite hits, short context, and frida.log supplements. Read query_frida_logs Pull frida.log and view a short keyword or time-window slice. Read query_hook_logs Pull runtime logs and query recent hook records from algorithmAidePro.db and frida.log. Read read_target_state Read the current target state, including config, AppSwitch, log sources, and LSPosed scope. Read search_hook_logs Search the structured hook log database by keyword across class, method, details, and call stack fields.

WRITE 6 tools

Write sync_appswitch_state Sync AppSwitch.json and logList.json, then verify both storage layers. Write sync_lsposed_scope Sync the LSPosed scope for AlgorithmAide and return the readback. Write apply_algorithm_aide_config Write files/config/<pkg>.json safely and verify the config provider readback. Write import_hook_json Low-level config import for compatibility. Prefer apply_algorithm_aide_config for normal use. Write replace_frida_script Replace a Frida script under /data/system/junge/<pkg>/frida and verify the write. Write save_hook_profile Save a hook configuration profile locally.

DESTRUCTIVE 1 tools

Destructive reset_target_config Reset the target config to an empty template and apply it through the verified workflow.

EXECUTE 5 tools

Execute run_verified_workflow Run the minimal verified loop: stop apps, write state, start AlgorithmAide, sync LSPosed, then optionally l... Execute inject_frida_script Enable one Frida script for a target package and sync config, AppSwitch, and LSPosed in one step. Execute add_custom_hooks Add or replace custom hook entries, then sync config, AppSwitch, LSPosed, and optionally relaunch the target. Execute add_r0capture_hooks Generate the built-in r0capture-style network hooks and apply them with the verified workflow. Execute apply_hook_profile Load a saved profile and apply it with the verified workflow.

// FAQ

How many tools does the Algorithmaide MCP server have? +

The Algorithmaide MCP server exposes 23 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Algorithmaide tools? +

Route the Algorithmaide server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Algorithmaide tools fall into? +

Algorithmaide tools are categorised as Read (11), Write (6), Destructive (1), Execute (5). Each category has a recommended default policy.

Enforce policy on every Algorithmaide tool call.

Start from Algorithmaide, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.