Low-level config import for compatibility. Prefer apply_algorithm_aide_config for normal use.
AI agents use import_hook_json 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 creates or modifies configuration data (hook configurations) on a real Android device. While config changes are typically reversible (placing it in Write rather than Destructive), the 'low-level' nature and the fact it's a direct import mechanism means it could persistently alter device behavior in ways that are difficult to undo without understanding the imported configuration.
From the tool's definition Tool is described as 'config import' which modifies system configuration on the Android device. The description explicitly notes it is 'low-level', suggesting direct manipulation of hook/runtime behavior without high-level safeguards.
Documented attack patterns abuse exactly the kind of access import_hook_json 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 import_hook_json:
{
"version": "1",
"default": "deny",
"tools": {
"import_hook_json": {
"limits": [
{
"counter": "import_hook_json_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} import_hook_json 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.
Low-level config import for compatibility. Prefer apply_algorithm_aide_config for normal use. 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 import_hook_json: 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.
import_hook_json 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 import_hook_json 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 import_hook_json. 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.
import_hook_json 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.