Search the structured hook log database by keyword across class, method, details, and call stack fields.
AI agents call search_hook_logs 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 queries existing log data across multiple fields (class, method, details, call stack) and returns results. No data is created, modified, deleted, or executed. It is a passive information retrieval operation with no side effects. The low severity reflects that misuse would only expose sensitive debugging information already captured in logs, not alter system state or trigger unintended actions.
From the tool's definition Tool performs search/query operations across 'structured hook log database' by keyword without modifying data. Description uses 'search' and 'by keyword' indicating read-only retrieval.
Documented attack patterns abuse exactly the kind of access search_hook_logs 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 search_hook_logs:
{
"version": "1",
"default": "deny",
"tools": {
"search_hook_logs": {}
}
}search_hook_logs 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.
Search the structured hook log database by keyword across class, method, details, and call stack fields. 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 search_hook_logs: 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.
search_hook_logs 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 search_hook_logs 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 search_hook_logs. 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.
search_hook_logs 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.