Low Risk

signal_list

Use when you need recent news, events, or market-moving signals for specific tickers or sectors. For SEC filing narrative use sec_report_search instead. Recent news + market events filtered by ticker / sector / time range. Each row is one signal: id, headline, summary, suggested_tickers, sector, ...

Part of the Drillr — The financial MCP for AI agents server.

signal_list is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DRILLR — THE FINANCIAL MCP FOR AI AGENTS →

Free to start. No card required.

AI agents call signal_list to retrieve information from Drillr — The financial MCP for AI agents without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though signal_list only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "signal_list": {}
  }
}

See the full Drillr — The financial MCP for AI agents policy for all 9 tools.

Get this rule live on your own Drillr — The financial MCP for AI agents server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DRILLR — THE FINANCIAL MCP FOR AI AGENTS →

View all 9 tools →

These attack patterns abuse exactly the kind of access signal_list gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so signal_list only ever does what you allow.

SECURE DRILLR — THE FINANCIAL MCP FOR AI AGENTS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the signal_list tool do? +

Use when you need recent news, events, or market-moving signals for specific tickers or sectors. For SEC filing narrative use sec_report_search instead. Recent news + market events filtered by ticker / sector / time range. Each row is one signal: id, headline, summary, suggested_tickers, sector, score, trigger_sources, earliest_trigger_event_time, created_at, tags. Continuously updating feed. Coverage: - ~6,900 tickers across US + ADRs of global companies - Cross-asset: equities, macro, geopolitics, commodities, crypto - Default sort by earliest_trigger_event_time DESC Parameters: - tickers (optional): array of tickers — returns signals whose suggested_tickers overlaps any of these - sector (optional): array of sector strings — returns signals whose sector overlaps any of these - from_date (optional): ISO 8601 timestamp; filter earliest_trigger_event_time >= from_date - to_date (optional): ISO 8601 timestamp; filter earliest_trigger_event_time <= to_date - order_by (optional, default earliest_trigger_event_time): 'created_at' | 'earliest_trigger_event_time' - limit (optional, default 20, max 100): max results - offset (optional, default 0): pagination offset. It is categorised as a Read tool in the Drillr — The financial MCP for AI agents MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on signal_list? +

Register the Drillr — The financial MCP for AI agents MCP server in PolicyLayer and add a rule for signal_list: 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 Drillr — The financial MCP for AI agents. Nothing to install.

What risk level is signal_list? +

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

Can I rate-limit signal_list? +

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

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

signal_list is provided by the Drillr — The financial MCP for AI agents MCP server (https://gateway.drillr.ai/mcp/data). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Drillr — The financial MCP for AI agents tool call.

Deterministic rules across all 9 Drillr — The financial MCP for AI agents tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.