list_available_dates
AI agents call list_available_dates to retrieve information from TrendRadar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to query available dates—likely from the TrendRadar aggregator's data store—to support other data retrieval operations. Listing dates is a non-destructive query that returns metadata about available data ranges. No modification, execution, deletion, or financial impact is implied.
From the tool's definition Tool name 'list_available_dates' indicates a retrieval operation that lists dates without modification. The empty description is uninformative, but the naming convention aligns with other Read-category sibling tools (get_latest_news, get_news_by_date,…
Attacks that exploit this kind of access
list_available_dates. It is categorised as a Read tool in the TrendRadar MCP Server, which means it retrieves data without modifying state.
Register the TrendRadar MCP server in PolicyLayer and add a rule for list_available_dates: 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 TrendRadar. Nothing to install.
list_available_dates 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 list_available_dates 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 list_available_dates. 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.
list_available_dates is provided by the TrendRadar MCP server (ssdsalesman/trendradar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →