whats_new
Recently updated tools, ranked by their real upstream push date (never by our re-crawl date). Coverage note: not every source exposes push dates yet.
This record as markdown: /tools/com-getagentictools-catalog/whats-new.md
What whats_new does on Catalog
AI agents call whats_new to retrieve information from Catalog without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | Look-back window in days (1-90, default 7) |
limit | integer | — | Maximum results to return (1-50, default 15) |
category | string | — | Restrict to one category; omit for all four |
Parameters from the server's own tool schema.
Why whats_new is rated Low
This tool queries and returns a list of recently updated tools from the catalog. It is purely a read/fetch operation with no writes, executions, or deletions. Misuse potential is minimal as it only surfaces publicly available catalog metadata.
From the tool's definition 'Recently updated tools, ranked by their real upstream push date' — retrieves/lists recently updated tools, no side effects
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs whats_new safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Catalog, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whats_new, this is the rule to start with:
whats_new 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 Catalog, apply this rule, and every whats_new call is checked against it from then on.
Questions about whats_new
Recently updated tools, ranked by their real upstream push date (never by our re-crawl date). Coverage note: not every source exposes push dates yet. It is categorised as a Read tool in the Catalog MCP Server, which means it retrieves data without modifying state.
whats_new accepts 3 parameters: days, limit, category. The full parameter table on this page comes from the server's own tool schema.
Register the Catalog MCP server in PolicyLayer and add a rule for whats_new: 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 Catalog. Nothing to install.
whats_new 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 whats_new 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 whats_new. 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.
whats_new is provided by the Catalog MCP server (https://getagentictools.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Catalog, and thousands of servers like it.
This server
Across the catalogue