predict_market_trajectory

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/predict-market-trajectory.md

WHAT IT DOES

What predict_market_trajectory does on Mcp Server

AI agents call predict_market_trajectory 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
`market_slug`	string	—	Market slug (metro), e.g. dallas, phoenix, northern-virginia — valid slugs come from rank_markets / get_market_dcpi_rank
`horizon_quarters`	integer	—	Forecast horizon in quarters (1-8, default 4); 2 = ~6 months ahead

Parameters from the server's own tool schema.

RISK

Why predict_market_trajectory is rated Low

The tool retrieves historical DCPI snapshot data and performs statistical forecasting (with confidence bands). It is purely analytical/read-only: it queries time-series history and returns projections. No data is created, modified, deleted, or any financial transaction initiated. Severity is low since misuse only risks acting on incorrect market forecasts.

From the tool's definition 'Forecast a DCPI market's near-term trajectory' and 'Projects excess_power_score and constraint_score forward' — this tool reads from DC Hub's historical time-series data and generates forecasts/projections without modifying any data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs predict_market_trajectory 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 predict_market_trajectory, this is the rule to start with:

predict_market_trajectory Allowed

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

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 predict_market_trajectory call is checked against it from then on.

FAQ

Questions about predict_market_trajectory

What does the predict_market_trajectory tool do? +

Forecast a DCPI market's near-term trajectory (next 1-8 quarters). Projects excess_power_score and constraint_score forward with confidence bands that WIDEN with horizon, from DC Hub's daily DCPI snapshot history — the only source that can, because it owns the time-series. Use to answer "is this market trending toward BUILD or AVOID?" or "will Dallas power stay tight over the next 6 months?". Params: market_slug (required, metro slug e.g. dallas, phoenix, northern-virginia — valid slugs come from rank_markets / get_market_dcpi_rank); horizon_quarters (optional 1-8, default 4; 2 = ~6 months out). Returns {market_slug, method, basis{history_points, history_span_days, slope_per_day, trend}, horizon_quarters, projection[{quarter_out, excess_power_score, excess_power_band, constraint_score, constraint_band}], caveat, snapshot_record}. HONEST: linear trend extrapolation, NOT a guarantee — bands widen with horizon and short history; needs >=3 daily snapshots or it declines. Do NOT use for a single point-in-time verdict (use get_market_dcpi_rank) or to rank many markets (use rank_markets). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does predict_market_trajectory accept? +

predict_market_trajectory accepts 2 parameters: market_slug, horizon_quarters. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on predict_market_trajectory? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for predict_market_trajectory: 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 predict_market_trajectory? +

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

Can I rate-limit predict_market_trajectory? +

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

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

predict_market_trajectory 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

The MCP Attack Database →

Guides

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