business.hunter.company
Find professional email addresses and company data for any domain — organization name, industry, employee count, tech stack, social profiles, email pattern, and verified contact emails with confidence scores, positions, departments, seniority levels. 50M+ domains indexed (Hunter.io)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/business.hunter.company.md
What business.hunter.company does on Apibase
AI agents call business.hunter.company to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Filter by email type: "personal" (name@domain) or "generic" (info@domain) |
limit | integer | — | Max number of emails to return (default 10, max 100) |
domain | string | Yes | Company domain name (e.g. "stripe.com", "google.com", "microsoft.com") |
department | string | — | Filter by department (e.g. "engineering", "sales", "marketing") |
Parameters from the server's own tool schema.
Why business.hunter.company is rated Low
Retrieves publicly available business intelligence and contact information without modifying data or executing code.
From the tool's definition Find professional email addresses and company data for any domain — organization name, industry, employee count
Attacks that exploit this kind of access
The rule that runs business.hunter.company safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For business.hunter.company, this is the rule to start with:
business.hunter.company 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 Apibase, apply this rule, and every business.hunter.company call is checked against it from then on.
Questions about business.hunter.company
Find professional email addresses and company data for any domain — organization name, industry, employee count, tech stack, social profiles, email pattern, and verified contact emails with confidence scores, positions, departments, seniority levels. 50M+ domains indexed (Hunter.io). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
business.hunter.company accepts 4 parameters: type, limit, domain, department. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for business.hunter.company: 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 Apibase. Nothing to install.
business.hunter.company 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 business.hunter.company 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 business.hunter.company. 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.
business.hunter.company is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue