get_deal_history

Get closed deal history with profit/loss.

SERVER:GT Protocol MCP Server SOURCEgt-protocol/mcp
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/gt-protocol-mcp/get-deal-history.md

What get_deal_history does on :GT Protocol MCP Server

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

Why get_deal_history is rated Low

This tool retrieves historical trading data (closed deals and their P&L) without creating, modifying, deleting, or executing any trades. It has no side effects on the trading system state. While it operates in a financial context (trading platform), it does not move money, commit financial obligations, or trigger any trading actions—it only queries past transaction records.

From the tool's definition Tool name 'get_deal_history' and description 'Get closed deal history with profit/loss' indicate data retrieval with no modification or execution of trades.

Questions about get_deal_history

What does the get_deal_history tool do? +

Get closed deal history with profit/loss. It is categorised as a Read tool in the :GT Protocol MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_deal_history? +

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

What risk level is get_deal_history? +

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

Can I rate-limit get_deal_history? +

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

How do I block get_deal_history completely? +

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

What MCP server provides get_deal_history? +

get_deal_history is provided by the :GT Protocol MCP Server MCP server (gt-protocol/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on :GT Protocol MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of :GT Protocol MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.