sg_disease_trend

Aggregate exact epidemiological weeks for disease labels matching the query and expose the frozen source coverage prominently.

SERVERMcp Singapore SOURCE@olano/mcp-singapore

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/olano-mcp-singapore/sg-disease-trend.md

WHAT IT DOES

What sg_disease_trend does on Mcp Singapore

AI agents call sg_disease_trend to retrieve information from Mcp Singapore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required
`disease`	string	Yes
`weeksBack`	integer	—
`weeks_back`	integer	—

Parameters from the server's own tool schema.

RISK

Why sg_disease_trend is rated Low

Even though sg_disease_trend only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sg_disease_trend 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_disease_trend, this is the rule to start with:

sg_disease_trend Allowed

sg_disease_trend is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sg_disease_trend": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Singapore, apply this rule, and every sg_disease_trend call is checked against it from then on.

FAQ

Questions about sg_disease_trend

What does the sg_disease_trend tool do? +

Aggregate exact epidemiological weeks for disease labels matching the query and expose the frozen source coverage prominently. It is categorised as a Read tool in the Mcp Singapore MCP Server, which means it retrieves data without modifying state.

What parameters does sg_disease_trend accept? +

sg_disease_trend accepts 3 parameters: disease, weeksBack, weeks_back. Required: disease. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sg_disease_trend? +

Register the Mcp Singapore MCP server in PolicyLayer and add a rule for sg_disease_trend: 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.

What risk level is sg_disease_trend? +

sg_disease_trend is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sg_disease_trend? +

Yes. Add a rate_limit block to the sg_disease_trend 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.

How do I block sg_disease_trend completely? +

Set action: deny in the PolicyLayer policy for sg_disease_trend. 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.

What MCP server provides sg_disease_trend? +

sg_disease_trend 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.

KEEP EXPLORING

More on Mcp Singapore, and thousands of servers like it.

This server

All 291 Mcp Singapore tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →