run_competitor_intake_scanner

WHAT IT DOES

What run_competitor_intake_scanner does on Quiet Protocol Growth Offense

AI agents call run_competitor_intake_scanner 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
`city`	string	—	Primary city or market.
`niche`	string	—	Business niche or vertical.
`businessUrl`	string	—	The business website URL.
`competitorUrl`	string	—	A competitor website URL.

Parameters from the server's own tool schema.

THE RISK

Low Risk

Why run_competitor_intake_scanner needs a policy

The tool performs a read/audit operation by scanning and comparing visible intake posture between two sites, then scoring the gap. It retrieves and analyzes publicly visible information without creating, modifying, executing, or deleting anything.

From the tool's definition 'Compare the visible intake posture of your site against a competitor and score where the competitive intake gap is opening' — this is a comparative analysis/scoring operation that reads and evaluates publicly visible data

Documented attack patterns abuse exactly the kind of access run_competitor_intake_scanner gives an agent:

POLICY

How to control run_competitor_intake_scanner

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_competitor_intake_scanner:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_competitor_intake_scanner": {}
  }
}

run_competitor_intake_scanner is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Quiet Protocol Growth Offense — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Quiet Protocol Growth Offense tools

Execute run_trust_stack_audit Scan a public website and score review signals, proof depth, expert identity, differentiat Read run_front_door_benchmark Benchmark the business front door using lead volume, customer value, and current intake pr Read run_response_time_loss_estimator Estimate lost bookings and revenue at risk caused by slow first response using lead volume Read run_review_velocity_benchmark Benchmark whether a business is creating enough fresh review proof based on total reviews, Read find_best_resource Recommend the most relevant public resources or kits for a niche and problem statement. Read get_benchmark Fetch one public benchmark profile by slug. Read get_kit Fetch one starter kit by slug, including bundled resource links and download metadata. Read get_resource Fetch one free resource by slug, including download metadata when available.

All 19 Quiet Protocol Growth Offense tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about run_competitor_intake_scanner

What does the run_competitor_intake_scanner tool do? +

Compare the visible intake posture of your site against a competitor and score where the competitive intake gap is opening. It is categorised as a Read tool in the Quiet Protocol Growth Offense MCP Server, which means it retrieves data without modifying state.

What parameters does run_competitor_intake_scanner accept? +

run_competitor_intake_scanner accepts 4 parameters: city, niche, businessUrl, competitorUrl. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_competitor_intake_scanner? +

Register the Quiet Protocol Growth Offense MCP server in PolicyLayer and add a rule for run_competitor_intake_scanner: 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.

What risk level is run_competitor_intake_scanner? +

run_competitor_intake_scanner is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit run_competitor_intake_scanner? +

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

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

run_competitor_intake_scanner 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.

Enforce policy on every Quiet Protocol Growth Offense tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

19 Quiet Protocol Growth Offense tools catalogued and risk-classified — across an index of 43,000+ MCP servers.