AI agents use save_hook_profile 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 a hook configuration profile on the local filesystem. While the operation is reversible (unlike Destructive), it modifies persistent state. Severity is medium because misconfigured hook profiles could affect instrumentation behavior on a real Android device, but the direct impact is localized to profile storage without immediate execution or data destruction.
From the tool's definition Tool name 'save_hook_profile' and description 'Save a hook configuration profile locally' indicate data creation/modification. The action is reversible (profiles can be overwritten or deleted), and aligns with write semantics.
Documented attack patterns abuse exactly the kind of access save_hook_profile 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 save_hook_profile:
{
"version": "1",
"default": "deny",
"tools": {
"save_hook_profile": {
"limits": [
{
"counter": "save_hook_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_hook_profile 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.
Save a hook configuration profile locally. 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 save_hook_profile: 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.
save_hook_profile 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 save_hook_profile 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 save_hook_profile. 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.
save_hook_profile 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.