AI agents call sg_ecda_centres_near 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 queries and retrieves childcare centre information based on postal code proximity. It performs a read-only search operation with no data modification, deletion, or external execution capabilities. The blast radius of misuse is minimal—worst case an AI agent retrieves unwanted location data about childcare centres, which is already public government data.
From the tool's definition Tool name 'sg_ecda_centres_near' and description 'Find childcare centres whose postal_code shares a prefix with' indicate a query/search operation that retrieves location-based data without modification or side effects.
Attacks that exploit this kind of access
Find childcare centres whose postal_code shares a prefix with. 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_ecda_centres_near: 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_ecda_centres_near 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_ecda_centres_near 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_ecda_centres_near. 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_ecda_centres_near 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 →