get_dwelling_type_population
AI agents call get_dwelling_type_population to retrieve information from OneMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves population data aggregated by dwelling type—a straightforward query operation with no side effects, data modification, execution of code, or destructive capabilities. It fits the 'Read' category as it queries statistical data. Severity is low because exposing population statistics carries minimal risk of harm if misused by an AI agent.
From the tool's definition Tool name 'get_dwelling_type_population' indicates retrieval of population statistics by dwelling type. Server description states it provides access to 'population statistics' as a read-only query capability.
Attacks that exploit this kind of access
get_dwelling_type_population. It is categorised as a Read tool in the OneMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OneMap MCP Server MCP server in PolicyLayer and add a rule for get_dwelling_type_population: 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 OneMap MCP Server. Nothing to install.
get_dwelling_type_population 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 get_dwelling_type_population 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 get_dwelling_type_population. 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.
get_dwelling_type_population is provided by the OneMap MCP Server MCP server (linzele/mcp-onemap). 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 →