AI agents call sg_unemployment_history to retrieve information from Sgdata without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns unemployment rate statistics from a Singapore government dataset. It is a pure data retrieval operation with no side effects, no irreversible actions, and no code execution. The blast radius of misuse is minimal—an AI agent could only retrieve unemployment statistics that are already public data, posing no security, financial, or operational risk.
From the tool's definition Tool name 'sg_unemployment_history' and description 'Unemployment rate time series for a given residential status' indicate retrieval of historical statistical data with no modification, creation, deletion, or execution of code.
Attacks that exploit this kind of access
Unemployment rate time series for a given residential status. It is categorised as a Read tool in the Sgdata MCP Server, which means it retrieves data without modifying state.
Register the Sgdata MCP server in PolicyLayer and add a rule for sg_unemployment_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 Sgdata. Nothing to install.
sg_unemployment_history 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 sg_unemployment_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.
Set action: deny in the PolicyLayer policy for sg_unemployment_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.
sg_unemployment_history is provided by the Sgdata MCP server (sypherin/sgdata-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 →