AI agents call query_history to retrieve information from Wyckoff Trading Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'query_history' strongly suggests data retrieval with no side effects. While the empty description reduces confidence slightly, the naming convention and sibling tools (analyze_stock, run_backtest) that perform calculations on historical data indicate this is a Read operation. No write, delete, execute, or financial transaction capabilities are implied.
From the tool's definition Tool name 'query_history' indicates retrieval of historical data with no description provided. Based on context (Wyckoff Trading Agent analyzing stock data), this likely queries historical price/volume data for analysis purposes.
Documented attack patterns abuse exactly the kind of access query_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wyckoff Trading Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_history:
{
"version": "1",
"default": "deny",
"tools": {
"query_history": {}
}
}query_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.
query_history. It is categorised as a Read tool in the Wyckoff Trading Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wyckoff Trading Agent MCP Server MCP server in PolicyLayer and add a rule for query_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 Wyckoff Trading Agent MCP Server. Nothing to install.
query_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 query_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 query_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.
query_history is provided by the Wyckoff Trading Agent MCP Server MCP server (youngcan-wang/wyckofftradingagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Wyckoff Trading Agent MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Wyckoff Trading Agent MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.