AI agents call sg_dengue_clusters 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 retrieves and queries real-time public health information from Singapore's government data portal. It has no side effects—it does not create, modify, delete, or execute operations. The use cases cited (health risk assessment, property evaluation, travel safety) are all read-only analytical tasks.
From the tool's definition Tool name 'sg_dengue_clusters' and description 'Get active dengue cluster locations' indicate retrieval of public health data without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get active dengue cluster locations in Singapore with case counts and GeoJSON boundaries. Use for health risk assessment, property evaluation, or travel safety in Singapore. 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_dengue_clusters: 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_dengue_clusters 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_dengue_clusters 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_dengue_clusters. 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_dengue_clusters 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 →