recent_changes

SERVER19hz SOURCEhttps://gateway.pipeworx.io/19hz/mcp

Low RISK CLASS

Category Read

Parameters 33 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pipeworx-io-19hz/recent-changes.md

WHAT IT DOES

What recent_changes does on 19hz

AI agents call recent_changes to retrieve information from 19hz 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
`type`	string	Yes	Entity type. Only "company" supported today.
`since`	string	Yes	Window start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
`value`	string	Yes	Ticker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Parameters from the server's own tool schema.

RISK

Why recent_changes is rated Low

This tool passively retrieves publicly available information about company changes and news from multiple data sources. It fans out queries but performs no side effects—no data is created, modified, deleted, or executed. The tool is a data aggregation and search instrument with no blast radius beyond information disclosure. Severity is low because the data returned is public/structured information about companies.

From the tool's definition Tool description explicitly states it retrieves 'change feed', 'filings', 'news mentions', and 'patents granted' from external sources (SEC EDGAR, GDELT, GNews, USPTO).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs recent_changes safely

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

recent_changes Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect 19hz, apply this rule, and every recent_changes call is checked against it from then on.

FAQ

Questions about recent_changes

What does the recent_changes tool do? +

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.

What parameters does recent_changes accept? +

recent_changes accepts 3 parameters: type, since, value. Required: type, since, value. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on recent_changes? +

Register the 19hz MCP server in PolicyLayer and add a rule for recent_changes: 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 19hz. Nothing to install.

What risk level is recent_changes? +

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

Can I rate-limit recent_changes? +

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

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

recent_changes is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 19hz, and thousands of servers like it.

This server

All 32 19hz tools →

Across the catalogue

review_changes on MCP Server PR Pilot → The MCP Attack Database →

Guides

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