get_signal_history

Return the detected SignalEvent rows for a single trigger — each event records whether the poll found changes, a summary, and the raw scrape. Returns {data: SignalEvent[]}.

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/get-signal-history.md

WHAT IT DOES

What get_signal_history does on Max MCP Server

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

RISK

Why get_signal_history is rated Low

get_signal_history fetches and returns existing signal event records. There are no side effects, state modifications, code execution, data deletion, or financial implications. The tool merely queries and presents historical polling data to the user. This is a straightforward Read operation with low blast radius — misuse would only expose sensitive information contained in those events, not cause structural damage.

From the tool's definition Tool description states 'Return the detected SignalEvent rows' — it retrieves historical signal event data without modifying, deleting, or executing external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_signal_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_signal_history, this is the rule to start with:

get_signal_history Allowed

get_signal_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_signal_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every get_signal_history call is checked against it from then on.

FAQ

Questions about get_signal_history

What does the get_signal_history tool do? +

Return the detected SignalEvent rows for a single trigger — each event records whether the poll found changes, a summary, and the raw scrape. Returns {data: SignalEvent[]}. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_signal_history? +

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

What risk level is get_signal_history? +

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

Can I rate-limit get_signal_history? +

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

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

get_signal_history is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Max MCP Server, and thousands of servers like it.

This server

All 415 Max MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →