waiaas_hl_get_trade_history
AI agents call waiaas_hl_get_trade_history to retrieve information from Waiaas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name pattern, this appears to be a getter function that retrieves historical trade information from a wallet or trading system. This is a non-destructive read operation with no side effects. The description is empty, which slightly reduces confidence, but the naming convention strongly suggests read-only functionality.
From the tool's definition Tool name contains 'get_trade_history' which indicates data retrieval. The 'get' prefix is characteristic of read-only operations. The suffix 'history' further confirms this is querying historical data without modification.
Documented attack patterns abuse exactly the kind of access waiaas_hl_get_trade_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for waiaas_hl_get_trade_history:
{
"version": "1",
"default": "deny",
"tools": {
"waiaas_hl_get_trade_history": {}
}
}waiaas_hl_get_trade_history 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.
waiaas_hl_get_trade_history. It is categorised as a Read tool in the Waiaas MCP Server, which means it retrieves data without modifying state.
Register the Waiaas MCP server in PolicyLayer and add a rule for waiaas_hl_get_trade_history: 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 Waiaas. Nothing to install.
waiaas_hl_get_trade_history 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 waiaas_hl_get_trade_history 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 waiaas_hl_get_trade_history. 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.
waiaas_hl_get_trade_history is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, 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.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.