wa_contractor_recent_changes
List material Washington contractor-registration changes observed by LiveDataLink's official daily snapshot pipeline. Filter by observed timestamp, change type, or trade. Missing source rows are never labeled revoked; only observed field transitions are returned.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/wa-contractor-recent-changes.md
What wa_contractor_recent_changes does on Livedatalink
AI agents call wa_contractor_recent_changes 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 | integer | — | Maximum rows; default 20. |
since | string | — | ISO date or timestamp. Defaults to 30 days ago. |
trade | string | — | Optional specialty/trade substring. |
offset | integer | — | Rows to skip for pagination. |
change_type | string | — | Optional material transition type. |
Parameters from the server's own tool schema.
Why wa_contractor_recent_changes is rated Low
Even though wa_contractor_recent_changes 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_recent_changes 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_recent_changes, this is the rule to start with:
wa_contractor_recent_changes 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_recent_changes call is checked against it from then on.
Questions about wa_contractor_recent_changes
List material Washington contractor-registration changes observed by LiveDataLink's official daily snapshot pipeline. Filter by observed timestamp, change type, or trade. Missing source rows are never labeled revoked; only observed field transitions are returned. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
wa_contractor_recent_changes accepts 5 parameters: limit, since, trade, offset, change_type. 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_recent_changes: 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_recent_changes 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_recent_changes 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_recent_changes. 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_recent_changes 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