AI agents call sg_rainfall to retrieve information from Sg Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available weather data without side effects. It performs a simple data lookup operation analogous to checking a weather website. There is no risk of data modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an agent could at worst make redundant queries or display incorrect rainfall information, neither of which causes harm.
From the tool's definition Tool 'sg_rainfall' is described as retrieving 'real-time rainfall readings' from weather stations with no modification, creation, deletion, or execution capability. The action is purely observational: 'Use to check if it is currently raining.'
Attacks that exploit this kind of access
Get real-time rainfall readings from 50+ weather stations across Singapore. Use to check if it is currently raining in specific areas. It is categorised as a Read tool in the Sg Data MCP Server, which means it retrieves data without modifying state.
Register the Sg Data MCP server in PolicyLayer and add a rule for sg_rainfall: 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 Sg Data. Nothing to install.
sg_rainfall 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_rainfall 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_rainfall. 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_rainfall is provided by the Sg Data MCP server (vdineshk/sg-data-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 →