singstat_wages_history

Get bounded historical observations from SingStat table M182941.

SERVERMcp Singapore SOURCE@olano/mcp-singapore

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/olano-mcp-singapore/singstat-wages-history.md

WHAT IT DOES

What singstat_wages_history does on Mcp Singapore

AI agents call singstat_wages_history to retrieve information from Mcp Singapore 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
`series`	string	—
`periods`	integer	—

Parameters from the server's own tool schema.

RISK

Why singstat_wages_history is rated Low

Even though singstat_wages_history 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

RECOMMENDED RULE

The rule that runs singstat_wages_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Singapore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For singstat_wages_history, this is the rule to start with:

singstat_wages_history Allowed

singstat_wages_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "singstat_wages_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about singstat_wages_history

What does the singstat_wages_history tool do? +

Get bounded historical observations from SingStat table M182941. It is categorised as a Read tool in the Mcp Singapore MCP Server, which means it retrieves data without modifying state.

What parameters does singstat_wages_history accept? +

singstat_wages_history accepts 2 parameters: series, periods. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on singstat_wages_history? +

Register the Mcp Singapore MCP server in PolicyLayer and add a rule for singstat_wages_history: 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 Mcp Singapore. Nothing to install.

What risk level is singstat_wages_history? +

singstat_wages_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit singstat_wages_history? +

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

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

singstat_wages_history is provided by the Mcp Singapore MCP server (@olano/mcp-singapore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Singapore, and thousands of servers like it.

This server

All 291 Mcp Singapore tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →