trend_query

Get time-bucketed trend data for a table (useful for monthly/weekly trend charts)

SERVERNowAIKit — ServiceNow AI Toolkit SOURCEnowaikit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/trend-query.md

WHAT IT DOES

What trend_query does on NowAIKit — ServiceNow AI Toolkit

AI agents call trend_query to retrieve information from NowAIKit — ServiceNow AI Toolkit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why trend_query is rated Low

This tool retrieves aggregated time-series data from a ServiceNow table for analysis and charting purposes. While it is fundamentally a Read operation (no modification or deletion), the medium severity reflects that an AI agent could use trend queries to systematically extract sensitive operational patterns, metrics, or historical data that might inform social engineering or reveal business intelligence.

From the tool's definition Tool description states 'Get time-bucketed trend data for a table', which retrieves and queries data for trend visualization. The verb 'Get' and the purpose (generating charts from historical data) indicate data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs trend_query safely

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

trend_query Allowed

trend_query 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": {
    "trend_query": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect NowAIKit — ServiceNow AI Toolkit, apply this rule, and every trend_query call is checked against it from then on.

FAQ

Questions about trend_query

What does the trend_query tool do? +

Get time-bucketed trend data for a table (useful for monthly/weekly trend charts). It is categorised as a Read tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on trend_query? +

Register the NowAIKit — ServiceNow AI Toolkit MCP server in PolicyLayer and add a rule for trend_query: 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 NowAIKit — ServiceNow AI Toolkit. Nothing to install.

What risk level is trend_query? +

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

Can I rate-limit trend_query? +

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

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

trend_query is provided by the NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.

This server

All 410 NowAIKit — ServiceNow AI Toolkit tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

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