edgar_insider_transactions
List recent Form 4 insider transaction filings for a company. Returns accession numbers and filing dates; for detailed transaction data, use edgar_filing_content on each.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/edgar-insider-transactions.md
What edgar_insider_transactions does on Livedatalink
AI agents call edgar_insider_transactions to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum rows to return (default 25, max 100). |
identifier | string | Yes | Ticker symbol or CIK. |
Parameters from the server's own tool schema.
Why edgar_insider_transactions is rated Low
This tool queries and retrieves publicly available SEC insider transaction filing metadata (Form 4 accession numbers and dates). It performs no side effects, creates no data, executes no code, and has no destructive or financial impact. It is a straightforward read operation against a public financial data source.
From the tool's definition Tool description states it 'List[s] recent Form 4 insider transaction filings' and 'Returns accession numbers and filing dates'. The verb 'list' and 'returns' indicate read-only retrieval of publicly available SEC filing metadata.
Attacks that exploit this kind of access
The rule that runs edgar_insider_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For edgar_insider_transactions, this is the rule to start with:
edgar_insider_transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every edgar_insider_transactions call is checked against it from then on.
Questions about edgar_insider_transactions
List recent Form 4 insider transaction filings for a company. Returns accession numbers and filing dates; for detailed transaction data, use edgar_filing_content on each. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
edgar_insider_transactions accepts 2 parameters: limit, identifier. Required: identifier. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for edgar_insider_transactions: 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 Livedatalink. Nothing to install.
edgar_insider_transactions 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 edgar_insider_transactions 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 edgar_insider_transactions. 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.
edgar_insider_transactions is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue