# get_inner_trade_data

Get company insider trading data.

Agent View of the PolicyLayer registry record for `get_inner_trade_data`. HTML page: https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-inner-trade-data

## Facts

- Tool: `get_inner_trade_data`
- Server: AKShare One MCP Server (`zwldarren/akshare-one-mcp`) — https://policylayer.com/tools/zwldarren-akshare-one-mcp.md
- Homepage: https://github.com/zwldarren/akshare-one-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `symbol` | string | no | Stock symbol/ticker (e.g. '000001') |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_inner_trade_data",
    "arguments": {}
  }
}
```

## Why get_inner_trade_data is rated Low

Insider trading data is publicly available financial information that companies must disclose. Retrieving this data has no side effects—it does not execute trades, modify records, or commit financial obligations. The tool's purpose is informational analysis, consistent with other Read category tools on this server.

From the tool's own definition: "Tool name 'get_inner_trade_data' and description 'Get company insider trading data' indicate data retrieval."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches AKShare One MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_inner_trade_data": {}
  }
}
```

## Other tools on AKShare One MCP Server (8)

- `get_balance_sheet` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-balance-sheet.md
- `get_cash_flow` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-cash-flow.md
- `get_financial_metrics` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-financial-metrics.md
- `get_hist_data` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-hist-data.md
- `get_income_statement` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-income-statement.md
- `get_news_data` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-news-data.md
- `get_realtime_data` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-realtime-data.md
- `get_time_info` — Read — https://policylayer.com/tools/zwldarren-akshare-one-mcp/get-time-info.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=zwldarren-akshare-one-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/zwldarren-akshare-one-mcp