abs_zalo_history_range
Read chat message history across hours (since_hours, up to 168h / 7 days) from local SQLite store to summarize group discussions without calling Zalo API.
This record as markdown: /tools/abs-zalo-bot/abs-zalo-history-range.md
What abs_zalo_history_range does on Abs Zalo Bot
AI agents call abs_zalo_history_range to retrieve information from Abs Zalo Bot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why abs_zalo_history_range is rated Low
Even though abs_zalo_history_range only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs abs_zalo_history_range safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Abs Zalo Bot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For abs_zalo_history_range, this is the rule to start with:
abs_zalo_history_range is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Abs Zalo Bot, apply this rule, and every abs_zalo_history_range call is checked against it from then on.
Questions about abs_zalo_history_range
Read chat message history across hours (since_hours, up to 168h / 7 days) from local SQLite store to summarize group discussions without calling Zalo API. It is categorised as a Read tool in the Abs Zalo Bot MCP Server, which means it retrieves data without modifying state.
Register the Abs Zalo Bot MCP server in PolicyLayer and add a rule for abs_zalo_history_range: 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 Abs Zalo Bot. Nothing to install.
abs_zalo_history_range 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 abs_zalo_history_range 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 abs_zalo_history_range. 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.
abs_zalo_history_range is provided by the Abs Zalo Bot MCP server (abs-zalo-bot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Abs Zalo Bot, and thousands of servers like it.
This server
Across the catalogue