get_changes

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/get-changes.md

WHAT IT DOES

What get_changes does on Mcp Server

AI agents call get_changes to retrieve information from Mcp Server 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
`limit`	integer	—	Max results to return (1-500; default varies by tool)
`since`	string	—	Return changes since this ISO-8601 timestamp (YYYY-MM-DD or full datetime) or shorthand "24h"/"7d"; default 24h

Parameters from the server's own tool schema.

RISK

Why get_changes is rated Low

get_changes is a read-only incremental sync tool that queries and retrieves data changes since a timestamp. It returns market data, facility information, M&A deals, and portfolio alerts—all retrieval operations with no side effects. The 'CAUTION → BUILD' verdict flips and alerts are read results, not actions that modify state.

From the tool's definition Tool description states it "pulls only the delta instead of re-fetching everything" and "Returns DCPI 7-day market movers, newly discovered facilities, new M&A deals + news" with "per-saved-site verdict flips, excess-power deltas, alerts fired." All described…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_changes safely

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

get_changes Allowed

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

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

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

FAQ

Questions about get_changes

What does the get_changes tool do? +

Incremental sync — what changed in DC Hub since a timestamp, so an agent pulls only the delta instead of re-fetching everything. Returns DCPI 7-day market movers, newly discovered facilities, new M&A deals + news — PLUS, for keyed callers with saved sites, a portfolio block answering "did MY sites move?": per-saved-site verdict flips (CAUTION → BUILD), excess-power deltas, alerts fired, and new facilities near each site since your last check. Pass since=<ISO-8601> or shorthand "24h"/"7d" (default 24h); cache the response generated_at and pass it back next call. Try: get_changes since=7d. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_changes accept? +

get_changes accepts 2 parameters: limit, since. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_changes? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for get_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 Server. Nothing to install.

What risk level is get_changes? +

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

Can I rate-limit get_changes? +

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

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

get_changes is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Server, and thousands of servers like it.

This server

All 79 Mcp Server tools →

Across the catalogue

review_changes on MCP Server PR Pilot →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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