wa_contractor_verify
Live Washington contractor registration lookup from the official L&I open-data API. Search by exact contractor license number or business name. Returns registration status, expiry, trade/type, public business details, separately reported insurance context, and official source links. Informational...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/wa-contractor-verify.md
What wa_contractor_verify does on Livedatalink
AI agents call wa_contractor_verify to retrieve information from Livedatalink 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 |
|---|---|---|---|
limit | number | — | Maximum candidate records when searching by business name. Default 5. |
business_name | string | — | Business name or distinctive name fragment. Used only when license_number is not supplied. |
license_number | string | — | Exact Washington contractor license number, if known. |
Parameters from the server's own tool schema.
Why wa_contractor_verify is rated Low
Even though wa_contractor_verify 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 wa_contractor_verify safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wa_contractor_verify, this is the rule to start with:
wa_contractor_verify 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 Livedatalink, apply this rule, and every wa_contractor_verify call is checked against it from then on.
Questions about wa_contractor_verify
Live Washington contractor registration lookup from the official L&I open-data API. Search by exact contractor license number or business name. Returns registration status, expiry, trade/type, public business details, separately reported insurance context, and official source links. Informational only: verify material decisions in L&I's Verify tool. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
wa_contractor_verify accepts 3 parameters: limit, business_name, license_number. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for wa_contractor_verify: 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 Livedatalink. Nothing to install.
wa_contractor_verify 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 wa_contractor_verify 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 wa_contractor_verify. 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.
wa_contractor_verify is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue