standing_intent
STANDING QUERIES with webhook push — register an intent once and 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: action ("register" default | "list" | "delete"), kind ("new_...
This record as markdown: /tools/cloud-dchub-mcp-server/standing-intent.md
What standing_intent does on Mcp Server
AI agents call standing_intent to permanently remove resources in Mcp Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | For news_keyword: the keyword/phrase to watch in title+summary, e.g. moratorium |
kind | string | — | Watch kind: "new_deal_in_market" | "news_keyword" | "permitting_change" |
state | string | — | For permitting_change: optional US state filter, e.g. MN |
action | string | — | "register" (default), "list" (your intents), or "delete" (needs intent_id) |
market | string | — | For new_deal_in_market: the market/region substring to watch, e.g. columbus |
intent_id | string | — | The intent_id to delete (from register/list) |
webhook_url | string | — | Your public HTTPS webhook endpoint (required for register) |
Parameters from the server's own tool schema.
Why standing_intent is rated Critical
An AI agent that decides to call standing_intent doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Server is gone. There is no undo for destructive operations.
Risk signalsAccepts URL/endpoint input (webhook_url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs 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 standing_intent, this is the rule to start with:
standing_intent is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every standing_intent call is checked against it from then on.
Questions about standing_intent
STANDING QUERIES with webhook push — register an intent once and 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: action ("register" default | "list" | "delete"), kind ("new_deal_in_market" watches deals in params market · "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 (public HTTPS only — private/internal hosts rejected), intent_id (for delete). Register returns {intent_id, secret} — SAVE the secret: every delivery carries X-DCHub-Signature: sha256=HMAC(secret, body). First evaluation initializes the watermark silently; growth fires the webhook; 5 straight delivery failures auto-disable the intent. Evaluated every ~2h. Try: standing_intent kind=news_keyword q=moratorium webhook_url=https://hooks.example.com/dchub. Do NOT use for one-shot reads (use get_news / list_transactions) or email alerts (use set_market_alert); this is machine-to-machine push. It is categorised as a Destructive tool in the Mcp Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
standing_intent accepts 7 parameters: q, kind, state, action, market, intent_id, webhook_url. 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 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.
standing_intent is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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 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.
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.
Across the catalogue