sg_labour_force
Official resident labour-force participation indicators. Canonical Olano tool: singstat_labour_force_history.
This record as markdown: /tools/olano-mcp-singapore/sg-labour-force.md
What sg_labour_force does on Mcp Singapore
AI agents call sg_labour_force to permanently remove resources in Mcp Singapore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why sg_labour_force is rated Critical
An AI agent that decides to call sg_labour_force doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Singapore is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs sg_labour_force 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 sg_labour_force, this is the rule to start with:
sg_labour_force is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Singapore, apply this rule, and every sg_labour_force call is checked against it from then on.
Questions about sg_labour_force
Official resident labour-force participation indicators. Canonical Olano tool: singstat_labour_force_history. It is categorised as a Destructive tool in the Mcp Singapore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Singapore MCP server in PolicyLayer and add a rule for sg_labour_force: 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.
sg_labour_force is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sg_labour_force 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 sg_labour_force. 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.
sg_labour_force 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.
More on Mcp Singapore, and thousands of servers like it.
Across the catalogue