Get trade deal history. Use EITHER a preset period OR a from/to date range, not both. Custom ranges limited to 90 days. Costs 2 weight.
AI agents call get_history to retrieve information from XBTFX MCP Trading Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves past trade deal history from the XBTFX trading account. It performs a read-only query operation with no ability to modify, delete, or execute trades. The 'weight' cost is a rate-limiting mechanism, not an indicator of destructive capability.
From the tool's definition Tool name 'get_history' and description 'Get trade deal history' indicate data retrieval with no modification or execution capability. The mention of preset periods and date ranges confirms it queries historical data without side effects.
Attacks that exploit this kind of access
Get trade deal history. Use EITHER a preset period OR a from/to date range, not both. Custom ranges limited to 90 days. Costs 2 weight. It is categorised as a Read tool in the XBTFX MCP Trading Server MCP Server, which means it retrieves data without modifying state.
Register the XBTFX MCP Trading Server MCP server in PolicyLayer and add a rule for get_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 XBTFX MCP Trading Server. Nothing to install.
get_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 get_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 get_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.
get_history is provided by the XBTFX MCP Trading Server MCP server (xbtfx/xbtfx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →