retail_sales_metadata
Get official metadata and schema for Retail Sales Index. Source: data.gov.sg dataset d_6b78d625911483860e162288a4000a0c (DOS).
This record as markdown: /tools/olano-mcp-singapore/retail-sales-metadata.md
What retail_sales_metadata does on Mcp Singapore
AI agents call retail_sales_metadata 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.
Why retail_sales_metadata is rated Low
Even though retail_sales_metadata 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
The rule that runs retail_sales_metadata 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 retail_sales_metadata, this is the rule to start with:
retail_sales_metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Singapore, apply this rule, and every retail_sales_metadata call is checked against it from then on.
Questions about retail_sales_metadata
Get official metadata and schema for Retail Sales Index. Source: data.gov.sg dataset d_6b78d625911483860e162288a4000a0c (DOS). It is categorised as a Read tool in the Mcp Singapore MCP Server, which means it retrieves data without modifying state.
Register the Mcp Singapore MCP server in PolicyLayer and add a rule for retail_sales_metadata: 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.
retail_sales_metadata 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 retail_sales_metadata 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 retail_sales_metadata. 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.
retail_sales_metadata 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.
More on Mcp Singapore, and thousands of servers like it.
This server
Across the catalogue