Get the structure/metadata for a Singapore statistics table by resourceId (get ids from search_tables): theme, subject, frequency, period coverage and the list of variables/series. Result is under Data.records.
Part of the Singstat Sg server.
Free to start. No card required.
AI agents call table_metadata to retrieve information from Singstat Sg without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though table_metadata only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"table_metadata": {}
}
}See the full Singstat Sg policy for all 23 tools.
These attack patterns abuse exactly the kind of access table_metadata gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get the structure/metadata for a Singapore statistics table by resourceId (get ids from search_tables): theme, subject, frequency, period coverage and the list of variables/series. Result is under Data.records.. It is categorised as a Read tool in the Singstat Sg MCP Server, which means it retrieves data without modifying state.
Register the Singstat Sg MCP server in PolicyLayer and add a rule for table_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 Singstat Sg. Nothing to install.
table_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 table_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 table_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.
table_metadata is provided by the Singstat Sg MCP server (https://gateway.pipeworx.io/singstat-sg/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Singstat Sg tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.