Get insider transactions (SEC Form 4) for a stock symbol
AI agents call get_insider_transactions to retrieve information from MCP Finnhub Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries publicly available SEC filing data without modifying, executing, deleting, or committing financial transactions. It is purely informational read access to historical insider trading information. No side effects or irreversible actions are possible.
From the tool's definition Tool retrieves insider transaction data from SEC Form 4 filings for a stock symbol. The description indicates data retrieval/querying with no modification capability.
Attacks that exploit this kind of access
Get insider transactions (SEC Form 4) for a stock symbol. It is categorised as a Read tool in the MCP Finnhub Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Finnhub Server MCP server in PolicyLayer and add a rule for get_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 MCP Finnhub Server. Nothing to install.
get_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 get_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 get_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.
get_insider_transactions is provided by the MCP Finnhub Server MCP server (nimblebraininc/mcp-finnhub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →