Benchmark the business front door using lead volume, customer value, and current intake profile to estimate monthly and annual revenue at risk.
AI agents call run_front_door_benchmark to retrieve information from Quiet Protocol Growth Offense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
niche | string | — | Business niche or vertical. |
averageValue | number | — | Average booked job, case, or customer value in USD. |
monthlyLeads | number | — | Approximate qualified inbound leads per month. |
frontDoorProfile | string | — | Current front-door operating posture. |
Parameters from the server's own tool schema.
The tool takes lead volume, customer value, and intake profile as inputs and produces revenue-at-risk estimates. This is a read/query operation — it calculates and returns analytical results without modifying data, executing code, or moving money.
From the tool's definition 'Benchmark the business front door' and 'estimate monthly and annual revenue at risk' — the tool performs estimation and analysis using input data, producing a read-only report
Documented attack patterns abuse exactly the kind of access run_front_door_benchmark gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Quiet Protocol Growth Offense, and nothing reaches the server without passing your rules. This is the rule we recommend for run_front_door_benchmark:
{
"version": "1",
"default": "deny",
"tools": {
"run_front_door_benchmark": {}
}
}run_front_door_benchmark is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Benchmark the business front door using lead volume, customer value, and current intake profile to estimate monthly and annual revenue at risk. It is categorised as a Read tool in the Quiet Protocol Growth Offense MCP Server, which means it retrieves data without modifying state.
run_front_door_benchmark accepts 4 parameters: niche, averageValue, monthlyLeads, frontDoorProfile. The full parameter table on this page comes from the server's own tool schema.
Register the Quiet Protocol Growth Offense MCP server in PolicyLayer and add a rule for run_front_door_benchmark: 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 Quiet Protocol Growth Offense. Nothing to install.
run_front_door_benchmark 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 run_front_door_benchmark 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 run_front_door_benchmark. 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.
run_front_door_benchmark is provided by the Quiet Protocol Growth Offense MCP server (joeroy2027/tqp-site). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Quiet Protocol Growth Offense, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Quiet Protocol Growth Offense tools catalogued and risk-classified — across an index of 43,000+ MCP servers.