talent_market_brief

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/talent-market-brief.md

WHAT IT DOES

What talent_market_brief does on Livedatalink

AI agents use talent_market_brief to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.

Parameter	Type	Required	Description
`metro`	string	—	Optional 5-digit CBSA/metro code (e.g. '12420' Austin, TX). OEWS metro coverage varies; an unmatched metro is noted, not fatal.
`state`	string	—	Optional 2-letter state code or 2-digit FIPS (e.g. 'TX', '48'). Omit for a national read.
`soc_code`	string	—	Explicit 6-digit SOC occupation code, with or without a dash (e.g. '29-1141' registered nurses, '15-1252' software developers). Overrides 'occupation'.
`occupation`	string	Yes	Free-text occupation to map to a SOC code (e.g. 'registered nurses', 'software developers', 'electricians'). Provide this or 'soc_code'.

Parameters from the server's own tool schema.

RISK

Why talent_market_brief is rated Medium

An AI agent can call talent_market_brief faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs talent_market_brief 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 talent_market_brief, this is the rule to start with:

talent_market_brief Rate-limited

talent_market_brief stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "talent_market_brief": {
      "limits": [
        {
          "counter": "talent_market_brief_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every talent_market_brief call is checked against it from then on.

FAQ

Questions about talent_market_brief

What does the talent_market_brief tool do? +

One-call 'can I hire this role here, and at what cost' read for an occupation in a US geography. Joins two independent federal sources: BLS OEWS (Occupational Employment and Wage Statistics, keyless) for the occupation's employment LEVEL and wage distribution (mean plus 10th / 50th-median / 90th annual percentiles) in the area, and US Census ACS labor-force context (civilian labor force and local unemployment rate - needs a Census API key) to band how TIGHT / BALANCED / SLACK the local hiring market is. Pass an 'occupation' (e.g. 'registered nurses', 'software developers') or an explicit 'soc_code' (e.g. '29-1141'), and an optional 'state' or 'metro' (defaults to national). Returns a readable brief with a headline (employment, median/mean wage, market tightness), the wage percentiles, and per-source evidence. The BLS OEWS leg is the core signal and is keyless; the Census leg degrades gracefully if no key is set. Informational, NOT a guarantee that a role can be filled at any given wage. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does talent_market_brief accept? +

talent_market_brief accepts 4 parameters: metro, state, soc_code, occupation. Required: occupation. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on talent_market_brief? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for talent_market_brief: 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.

What risk level is talent_market_brief? +

talent_market_brief is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit talent_market_brief? +

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

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

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

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 280 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →