"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), GDEL...
AI agents call recent_changes to retrieve information from Mcp Ygoprodeck without modifying anything — 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.
recent_changes retrieves and aggregates publicly available information about company updates, SEC filings, news mentions, and patent grants. It queries existing data sources (SEC EDGAR, news APIs, USPTO) without creating, modifying, deleting, or executing any side effects. This is a classic Read operation.
From the tool's definition Tool description states it returns a 'change feed' and 'fans out to SEC EDGAR (filings), GDELT→GNews (news mentions), USPTO (patents granted)' — all read-only data retrieval operations with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
"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 Mcp Ygoprodeck MCP Server, which means it retrieves data without modifying state.
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.
Register the Mcp Ygoprodeck 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 Mcp Ygoprodeck. Nothing to install.
recent_changes 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 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.
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.
recent_changes is provided by the Mcp Ygoprodeck MCP server (https://gateway.pipeworx.io/ygoprodeck/mcp). 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 →