register_standing_intent
Use this when the user wants a webhook when data center deals change: Register a STANDING QUERY with webhook push — DC Hub POSTs an HMAC-signed webhook to YOUR https URL whenever matches grow (push, not poll: "notify my orchestrator on any new deal in Columbus"). Requires a key. Params: kind ("ne...
This record as markdown: /tools/cloud-dchub-mcp-server/register-standing-intent.md
What register_standing_intent does on Mcp Server
AI agents use register_standing_intent to create or update resources in Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | For news_keyword: the keyword/phrase to watch in title+summary, e.g. moratorium |
kind | string | Yes | Watch kind: "new_deal_in_market" | "news_keyword" | "permitting_change" | "capacity" (a Capacity Source requirement, emailed, no webhook) |
name | string | — | For capacity: your human's full name, exactly as given; never invent it |
role | string | — | For capacity: your human's role or title |
notes | string | — | For capacity: anything else about the requirement; leave out anything that identifies your human |
state | string | — | For permitting_change: optional US state filter, e.g. MN |
market | string | — | For new_deal_in_market: the market/region substring to watch, e.g. columbus |
states | string | — | For capacity: comma-separated US states, e.g. "TX, AZ" |
company | string | — | For capacity: your human's company |
markets | string | — | For capacity: comma-separated markets, e.g. "Dallas, Phoenix" |
regions | string | — | For capacity: comma-separated regions from north_america, latin_america, europe, asia_pacific, middle_east_africa (aliases emea, apac, latam, americas) |
use_case | string | — | For capacity: what the capacity is for, e.g. "AI inference" |
Parameters from the server's own tool schema.
Why register_standing_intent is rated Medium
Creates persistent monitoring configuration that triggers external notifications; reversible registration with side effects.
From the tool's definition Register webhook, POST to YOUR https URL, requires key, matches grow
Risk signalsAccepts URL/endpoint input (webhook_url) · High parameter count (22 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs register_standing_intent 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 register_standing_intent, this is the rule to start with:
register_standing_intent stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every register_standing_intent call is checked against it from then on.
Questions about register_standing_intent
Use this when the user wants a webhook when data center deals change: Register a STANDING QUERY with webhook push — DC Hub POSTs an HMAC-signed webhook to YOUR https URL whenever matches grow (push, not poll: "notify my orchestrator on any new deal in Columbus"). Requires a key. Params: kind ("new_deal_in_market" watches deals in the market param · "news_keyword" watches news matching q · "permitting_change" watches published permitting intel, optionally per state), market / q / state (the watch parameter for the chosen kind), webhook_url (your public HTTPS endpoint — private/internal hosts are rejected). Returns {intent_id, secret} — SAVE the secret: every delivery carries X-DCHub-Signature: sha256=HMAC(secret, body). Answers "notify my system whenever a new moratorium appears", "push me new matches instead of making me poll", "tell my orchestrator when a deal lands in Columbus". Try: register_standing_intent kind=news_keyword q=moratorium webhook_url=https://hooks.example.com/dchub. kind="capacity" instead registers a standing CAPACITY REQUIREMENT with DC Hub Capacity Source (no webhook_url): target_mw or target_kw, markets / states / regions / countries (comma-separated), optional…. It is categorised as a Write tool in the Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
register_standing_intent accepts 12 parameters: q, kind, name, role, notes, state, market, states, company, markets, regions, use_case. Required: kind. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for register_standing_intent: 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.
register_standing_intent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_standing_intent 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 register_standing_intent. 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.
register_standing_intent 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.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue