AI agents call list_hook_profiles to retrieve information from Algorithmaide without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple enumeration of existing hook profiles stored locally. It queries or lists data without creating, modifying, deleting, or executing anything. The action is read-only and has minimal security impact even if called arbitrarily by an agent.
From the tool's definition Tool name is 'list_hook_profiles' and description states it 'List locally saved hook configuration profiles' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_hook_profiles 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 list_hook_profiles:
{
"version": "1",
"default": "deny",
"tools": {
"list_hook_profiles": {}
}
}list_hook_profiles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List locally saved hook configuration profiles. It is categorised as a Read tool in the Algorithmaide MCP Server, which means it retrieves data without modifying state.
Register the Algorithmaide MCP server in PolicyLayer and add a rule for list_hook_profiles: 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.
list_hook_profiles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_hook_profiles 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 list_hook_profiles. 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.
list_hook_profiles 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.