trades.history

Retrieve past copy trades from the database with optional filters by trader address or status. Returns trade details including entry price, P&L, and market info.

SERVERPolymarket Agent Mcp SOURCEdemwick/polymarket-agent-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/demwick-polymarket-agent-mcp/trades.history.md

WHAT IT DOES

What trades.history does on Polymarket Agent Mcp

AI agents call trades.history to retrieve information from Polymarket Agent Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why trades.history is rated Low

Tool retrieves historical trade data without modifying, deleting, or executing transactions.

From the tool's definition Retrieve past copy trades from the database with optional filters

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs trades.history safely

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

trades.history Allowed

trades.history 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": {
    "trades.history": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Polymarket Agent Mcp, apply this rule, and every trades.history call is checked against it from then on.

FAQ

Questions about trades.history

What does the trades.history tool do? +

Retrieve past copy trades from the database with optional filters by trader address or status. Returns trade details including entry price, P&L, and market info. It is categorised as a Read tool in the Polymarket Agent Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on trades.history? +

Register the Polymarket Agent MCP server in PolicyLayer and add a rule for trades.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 Polymarket Agent Mcp. Nothing to install.

What risk level is trades.history? +

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

Can I rate-limit trades.history? +

Yes. Add a rate_limit block to the trades.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 trades.history completely? +

Set action: deny in the PolicyLayer policy for trades.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 trades.history? +

trades.history is provided by the Polymarket Agent MCP server (demwick/polymarket-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Polymarket Agent, and thousands of servers like it.

This server

All 48 Polymarket Agent tools →

Across the catalogue

The MCP Attack Database →

Guides

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