enquiry_describe
Read first. States plainly what submit_enquiry does on 409A Cost: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
This record as markdown: /tools/com-409acost-site/enquiry-describe.md
What enquiry_describe does on Site
AI agents call enquiry_describe to retrieve information from Site without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why enquiry_describe is rated Low
Even though enquiry_describe only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs enquiry_describe 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 enquiry_describe, this is the rule to start with:
enquiry_describe is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Site, apply this rule, and every enquiry_describe call is checked against it from then on.
Questions about enquiry_describe
Read first. States plainly what submit_enquiry does on 409A Cost: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms. It is categorised as a Read tool in the Site MCP Server, which means it retrieves data without modifying state.
Register the Site MCP server in PolicyLayer and add a rule for enquiry_describe: 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.
enquiry_describe is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the enquiry_describe 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 enquiry_describe. 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.
enquiry_describe 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.
More on Site, and thousands of servers like it.
This server
Across the catalogue