query_temporal_signals
Search and retrieve temporal signals with filtering by entity, signal type, status, and date range. Returns formatted signal records from the local temporal store.
This record as markdown: /tools/io-github-homenshum-nodebench/query-temporal-signals.md
What query_temporal_signals does on Nodebench
AI agents call query_temporal_signals 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 query_temporal_signals is rated Low
The tool's core function is to search and retrieve data from a local temporal store. It performs no creation, modification, deletion, or execution of external operations. The filtering and date range parameters are standard retrieval constraints.
From the tool's definition Tool description states 'Search and retrieve temporal signals' with 'filtering' and 'Returns formatted signal records' — clearly a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs query_temporal_signals 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 query_temporal_signals, this is the rule to start with:
query_temporal_signals 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 query_temporal_signals call is checked against it from then on.
Questions about query_temporal_signals
Search and retrieve temporal signals with filtering by entity, signal type, status, and date range. Returns formatted signal records from the local temporal store. 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 query_temporal_signals: 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.
query_temporal_signals 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 query_temporal_signals 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 query_temporal_signals. 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.
query_temporal_signals 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