submit_enquiry

SERVERSite SOURCEhttps://409acost.com/mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-409acost-site/submit-enquiry.md

WHAT IT DOES

What submit_enquiry does on Site

AI agents use submit_enquiry to create or update resources in Site, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Site environment.

Parameter	Type	Required	Description
`answers`	object	Yes	the person's answers, keyed by field key
`consent`	boolean	Yes	true only when the person has agreed to: Send my contact details to up to three relevant 409A valuation providers, chosen by 409A Cost, who'll contact me direct
`confirmation`	string	—	the confirmation token from step 1, after the person has approved the summary

Parameters from the server's own tool schema.

RISK

Why submit_enquiry is rated Medium

An AI agent can call submit_enquiry faster than any human can review: one bad instruction and it creates or modifies resources in Site by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs submit_enquiry safely

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

submit_enquiry Rate-limited

submit_enquiry 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": {
    "submit_enquiry": {
      "limits": [
        {
          "counter": "submit_enquiry_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 Site, apply this rule, and every submit_enquiry call is checked against it from then on.

FAQ

Questions about submit_enquiry

What does the submit_enquiry tool do? +

Submits an enquiry to 409A Cost — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three relevant 409A valuation providers, chosen by 409A Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them.". It is categorised as a Write tool in the Site MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does submit_enquiry accept? +

submit_enquiry accepts 3 parameters: answers, consent, confirmation. Required: answers, consent. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on submit_enquiry? +

Register the Site MCP server in PolicyLayer and add a rule for submit_enquiry: 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 Site. Nothing to install.

What risk level is submit_enquiry? +

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

Can I rate-limit submit_enquiry? +

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

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

submit_enquiry is provided by the Site MCP server (https://409acost.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Site, and thousands of servers like it.

This server

All 5 Site tools →

Across the catalogue

The MCP Attack Database →

Guides

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