AI agents call sg_tourism_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 retrieves historical tourism receipt data from Singapore government datasets (data.gov.sg). It is a read-only query operation that fetches time series information without any side effects, data modification, code execution, or destructive capabilities. The low severity reflects minimal risk from misuse—retrieving historical tourism statistics poses no significant security, financial, or operational threat.
From the tool's definition Tool name 'sg_tourism_history' and description 'Tourism receipts time series for a specific component' indicate data retrieval of historical time series information with no modification or execution capabilities.
Attacks that exploit this kind of access
Tourism receipts time series for a specific component. 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_tourism_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_tourism_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_tourism_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_tourism_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_tourism_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 →