getSignalTimeseries
Get time-series signal data for research metrics like funding volume, entity mentions, or verification health over time.
This record as markdown: /tools/io-github-homenshum-nodebench/getsignaltimeseries.md
What getSignalTimeseries does on Nodebench
AI agents call getSignalTimeseries to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getSignalTimeseries is rated Low
This tool retrieves time-series metrics data for research and analysis purposes. It performs a read-only query operation on research signals, with no capability to modify, delete, execute commands, or affect system state. The blast radius of misuse is minimal—an attacker gains access to research metrics that are typically non-sensitive aggregate data.
From the tool's definition Tool name 'getSignalTimeseries' and description 'Get time-series signal data for research metrics like funding volume, entity mentions, or verification health over time' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs getSignalTimeseries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getSignalTimeseries, this is the rule to start with:
getSignalTimeseries 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 Nodebench, apply this rule, and every getSignalTimeseries call is checked against it from then on.
Questions about getSignalTimeseries
Get time-series signal data for research metrics like funding volume, entity mentions, or verification health over time. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for getSignalTimeseries: 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 Nodebench. Nothing to install.
getSignalTimeseries 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 getSignalTimeseries 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 getSignalTimeseries. 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.
getSignalTimeseries is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue