check_minimum_wage
PAID ($0.05). Compliance verdict: is a salary at, above or below the country's statutory minimum wage? Returns verdict, margin, the statutory floor and the legal instrument it rests on. Honest statuses when no enforceable floor exists or the period doesn't match the floor's period (cross-period c...
This record as markdown: /tools/dev-euroref-reference-data/check-minimum-wage.md
What check_minimum_wage does on Reference Data
AI agents call check_minimum_wage to retrieve information from Reference Data 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 |
|---|---|---|---|
amount | number | Yes | Wage to check, in the country's own currency |
period | string | Yes | Period the amount covers — must match the statutory floor's period |
api_key | string | — | API key (bypasses x402; metered for invoicing) |
country | string | Yes | ISO country code |
Parameters from the server's own tool schema.
Why check_minimum_wage is rated Low
Even though check_minimum_wage 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.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs check_minimum_wage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Reference Data, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_minimum_wage, this is the rule to start with:
check_minimum_wage 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 Reference Data, apply this rule, and every check_minimum_wage call is checked against it from then on.
Questions about check_minimum_wage
PAID ($0.05). Compliance verdict: is a salary at, above or below the country's statutory minimum wage? Returns verdict, margin, the statutory floor and the legal instrument it rests on. Honest statuses when no enforceable floor exists or the period doesn't match the floor's period (cross-period conversion is never guessed). Pass api_key if you have one; otherwise the response explains how to pay via x402. It is categorised as a Read tool in the Reference Data MCP Server, which means it retrieves data without modifying state.
check_minimum_wage accepts 4 parameters: amount, period, api_key, country. Required: amount, period, country. The full parameter table on this page comes from the server's own tool schema.
Register the Reference Data MCP server in PolicyLayer and add a rule for check_minimum_wage: 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 Reference Data. Nothing to install.
check_minimum_wage 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 check_minimum_wage 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 check_minimum_wage. 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.
check_minimum_wage is provided by the Reference Data MCP server (https://euroref.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Reference Data, and thousands of servers like it.
This server
Across the catalogue