get_lockup_expirations

Get upcoming IPO/secondary lockup expirations within a date window. Lockup

Server Signal8 MCP Server signal8ai/signal8-mcp
Category Read
Risk class Low
Parameters 00 required

What get_lockup_expirations does on Signal8 MCP Server

AI agents call get_lockup_expirations to retrieve information from Signal8 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_lockup_expirations needs a policy

This tool retrieves historical and scheduled lockup expiration data from SEC filings—a straightforward query operation with no side effects. While the information could inform trading decisions, the tool itself performs no financial transactions, executions, or modifications. It is purely informational, placing it in the Read category with low severity.

From the tool's definition Tool name 'get_lockup_expirations' and description 'Get upcoming IPO/secondary lockup expirations within a date window' indicate data retrieval only. No modification, deletion, execution, or financial transaction capabilities are present.

Questions about get_lockup_expirations

What does the get_lockup_expirations tool do? +

Get upcoming IPO/secondary lockup expirations within a date window. Lockup. It is categorised as a Read tool in the Signal8 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_lockup_expirations? +

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

What risk level is get_lockup_expirations? +

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

Can I rate-limit get_lockup_expirations? +

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

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

get_lockup_expirations is provided by the Signal8 MCP Server MCP server (signal8ai/signal8-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.