AI agents call sg_formations_history to retrieve information from Sgdata 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 historical business formation data from public government sources (data.gov.sg). It has no side effects, does not modify data, execute code, delete information, or involve financial transactions. It is a straightforward read-only data access tool with minimal risk if misused by an AI agent—at worst, excessive queries might cause rate-limiting but no data loss or damage.
From the tool's definition Tool name 'sg_formations_history' and description 'Get the historical time series of business formations' indicate data retrieval with no modification or destructive capability. The tool queries historical records from Singapore government datasets.
Attacks that exploit this kind of access
Get the historical time series of business formations for a. It is categorised as a Read tool in the Sgdata MCP Server, which means it retrieves data without modifying state.
Register the Sgdata MCP server in PolicyLayer and add a rule for sg_formations_history: 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 Sgdata. Nothing to install.
sg_formations_history 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_formations_history 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_formations_history. 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_formations_history is provided by the Sgdata MCP server (sypherin/sgdata-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 →