# 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.

Agent View of the PolicyLayer registry record for `whats_new`. HTML page: https://policylayer.com/tools/com-getagentictools-catalog/whats-new

## Facts

- Tool: `whats_new`
- Server: Catalog (`https://getagentictools.com/api/mcp`) — https://policylayer.com/tools/com-getagentictools-catalog.md
- Homepage: https://github.com/dmoka/getagentictools-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `days` | integer | no | Look-back window in days (1-90, default 7) |
| `limit` | integer | no | Maximum results to return (1-50, default 15) |
| `category` | string | no | Restrict to one category; omit for all four |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "whats_new",
    "arguments": {}
  }
}
```

## 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 own definition: "'Recently updated tools, ranked by their real upstream push date' — retrieves/lists recently updated tools, no side effects"

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Catalog:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "whats_new": {}
  }
}
```

## Other tools on Catalog (4)

- `ecosystem_stats` — Read — https://policylayer.com/tools/com-getagentictools-catalog/ecosystem-stats.md
- `get_tool` — Read — https://policylayer.com/tools/com-getagentictools-catalog/get-tool.md
- `list_categories` — Read — https://policylayer.com/tools/com-getagentictools-catalog/list-categories.md
- `search_tools` — Read — https://policylayer.com/tools/com-getagentictools-catalog/search-tools.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-getagentictools-catalog · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getagentictools-catalog