splitifi_jurisdiction_wages
Get BLS occupational wage data for a state and metro area. Returns median and 75th percentile hourly wages for use in personal injury damages calculations.
This record as markdown: /tools/io-github-mysplitifi-splitifi-mcp/splitifi-jurisdiction-wages.md
What splitifi_jurisdiction_wages does on Splitifi Intelligence MCP
AI agents call splitifi_jurisdiction_wages to retrieve information from Splitifi Intelligence MCP 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 |
|---|---|---|---|
state | string | Yes | 2-letter US state code (e.g. CA, TX) |
msa_code | string | — | BLS MSA area code (optional, e.g. 31080 for Los Angeles metro) |
Parameters from the server's own tool schema.
Why splitifi_jurisdiction_wages is rated Low
This tool performs a pure data retrieval operation against Bureau of Labor Statistics wage data. It queries existing public information without side effects, modifications, or irreversible actions. The severity is low because retrieving wage reference data poses minimal risk even if misused by an AI agent—it cannot alter records, execute commands, or commit financial transactions. It is informational only.
From the tool's definition Tool description explicitly states it 'returns' BLS occupational wage data with no modification or deletion capability. The function is to retrieve and retrieve only median and 75th percentile wage information for reference in damages calculations.
Attacks that exploit this kind of access
The rule that runs splitifi_jurisdiction_wages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Splitifi Intelligence MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For splitifi_jurisdiction_wages, this is the rule to start with:
splitifi_jurisdiction_wages 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 Splitifi Intelligence MCP, apply this rule, and every splitifi_jurisdiction_wages call is checked against it from then on.
Questions about splitifi_jurisdiction_wages
Get BLS occupational wage data for a state and metro area. Returns median and 75th percentile hourly wages for use in personal injury damages calculations. It is categorised as a Read tool in the Splitifi Intelligence MCP MCP Server, which means it retrieves data without modifying state.
splitifi_jurisdiction_wages accepts 2 parameters: state, msa_code. Required: state. The full parameter table on this page comes from the server's own tool schema.
Register the Splitifi Intelligence MCP server in PolicyLayer and add a rule for splitifi_jurisdiction_wages: 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 Splitifi Intelligence MCP. Nothing to install.
splitifi_jurisdiction_wages 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 splitifi_jurisdiction_wages 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 splitifi_jurisdiction_wages. 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.
splitifi_jurisdiction_wages is provided by the Splitifi Intelligence MCP server (splitifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Splitifi Intelligence, and thousands of servers like it.
This server
Across the catalogue