Get JOLTS turnover data for a Census region.
AI agents call get_regional_turnover to retrieve information from Thesma MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Bureau of Labor Statistics (BLS) JOLTS (Job Openings and Labor Turnover Survey) turnover data for a Census region. It performs a read-only query against public employment statistics data. There are no side effects, no data modification, no code execution, and no financial transactions. The worst-case misuse would be information disclosure of already-public BLS data, which poses minimal risk.
From the tool's definition Tool name 'get_regional_turnover' and description 'Get JOLTS turnover data for a Census region' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get JOLTS turnover data for a Census region. It is categorised as a Read tool in the Thesma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Thesma MCP Server MCP server in PolicyLayer and add a rule for get_regional_turnover: 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 Thesma MCP Server. Nothing to install.
get_regional_turnover 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 get_regional_turnover 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 get_regional_turnover. 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.
get_regional_turnover is provided by the Thesma MCP Server MCP server (thesma-dev/thesma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →