register_standing_intent

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/register-standing-intent.md

WHAT IT DOES

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"
`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
`webhook_url`	string	Yes	Your public HTTPS webhook endpoint (required)

Parameters from the server's own tool schema.

RISK

Why register_standing_intent is rated Medium

Creates persistent webhook subscriptions that modify server state reversibly; no financial impact or code execution.

From the tool's definition Register standing query with webhook push, POST to HTTPS URL, returns intent_id and secret.

Risk signalsAccepts URL/endpoint input (webhook_url) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "register_standing_intent": {
      "limits": [
        {
          "counter": "register_standing_intent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about register_standing_intent

What does the register_standing_intent tool do? +

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). First evaluation initializes the watermark silently; growth fires the webhook; 5 straight delivery failures auto-disable the intent. Evaluated every ~2h. 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. Do NOT use for one-shot reads (get_news / list_transactions) or email alerts (set_market_alert); this is machine-to-machine push. 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.

What parameters does register_standing_intent accept? +

register_standing_intent accepts 5 parameters: q, kind, state, market, webhook_url. Required: kind, webhook_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on register_standing_intent? +

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.

What risk level is register_standing_intent? +

register_standing_intent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit register_standing_intent? +

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.

How do I block register_standing_intent completely? +

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.

What MCP server provides register_standing_intent? +

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.

KEEP EXPLORING

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

This server

All 88 Mcp Server tools →

Across the catalogue

team_manager_register_agents on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →