history_deals_get

A read tool on the MCP Trader MCP server.

SERVERMCP Trader Server SOURCEaf7007/mcp-trader

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/af7007-mcp-trader/history-deals-get.md

WHAT IT DOES

What history_deals_get does on MCP Trader Server

AI agents call history_deals_get to retrieve information from MCP Trader Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why history_deals_get is rated Low

The 'get' verb and 'history' prefix strongly indicate a query/retrieval function that reads historical trading data. Even in a high-stakes financial trading context, merely reading historical deal information has no immediate financial impact or side effects. The lack of descriptive detail reduces confidence slightly, but the naming is sufficiently clear to categorize as Read rather than Financial.

From the tool's definition Tool name 'history_deals_get' indicates a retrieval operation ('get') on historical deal records. No description provided, but naming convention and sibling tools (buy_market, close_position, etc.) suggest this fetches past trading data without modifying it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs history_deals_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Trader Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For history_deals_get, this is the rule to start with:

history_deals_get Allowed

history_deals_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "history_deals_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Trader Server, apply this rule, and every history_deals_get call is checked against it from then on.

FAQ

Questions about history_deals_get

What does the history_deals_get tool do? +

history_deals_get is a read tool on the MCP Trader Server MCP server. It is categorised as a Read tool in the MCP Trader Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on history_deals_get? +

Register the MCP Trader Server MCP server in PolicyLayer and add a rule for history_deals_get: 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 MCP Trader Server. Nothing to install.

What risk level is history_deals_get? +

history_deals_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit history_deals_get? +

Yes. Add a rate_limit block to the history_deals_get 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.

How do I block history_deals_get completely? +

Set action: deny in the PolicyLayer policy for history_deals_get. 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.

What MCP server provides history_deals_get? +

history_deals_get is provided by the MCP Trader Server MCP server (af7007/mcp-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Trader Server, and thousands of servers like it.

This server

All 45 MCP Trader Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →